You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The repository's MVP is now based on the code in the main branch. We make all new changes to the develop branch and periodically merge develop into main
Contributors are now frequently submitting pull requests (PR) either merging main into develop or vice versa. This causes PRs with hundreds of submitted files.
Describe the solution you'd like
We need a GitHub Action added to the repository that counts the number of files submitted and fails if they exceed 20, which is a reasonable number in most cases.
The message must indicate that the contributor may either be merging into an incorrect branch or the source branch is incorrect.
If any scripting is required, this must be done in python3 with python black and pydocstyle linting and formatting rules applied. We have examples in the .github/workfows directory.
The action must run in its own section after the Continuous-Integration section in this workflow file
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.
Is your feature request related to a problem? Please describe.
main
branch. We make all new changes to thedevelop
branch and periodically mergedevelop
intomain
main
intodevelop
or vice versa. This causes PRs with hundreds of submitted files.Describe the solution you'd like
black
andpydocstyle
linting and formatting rules applied. We have examples in the.github/workfows
directory.Continuous-Integration
section in this workflow fileDescribe alternatives you've considered
Approach to be followed (optional)
Additional context
Potential internship candidates
The text was updated successfully, but these errors were encountered: