Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Actions Test - Fail When Too Many Files Submitted #1276

Closed
palisadoes opened this issue Dec 24, 2023 · 3 comments
Closed

GitHub Actions Test - Fail When Too Many Files Submitted #1276

palisadoes opened this issue Dec 24, 2023 · 3 comments
Labels

Comments

@palisadoes
Copy link
Contributor

Is your feature request related to a problem? Please describe.

  1. 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
  2. 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

  1. 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.
  2. The message must indicate that the contributor may either be merging into an incorrect branch or the source branch is incorrect.
  3. 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.
  4. The action must run in its own section after the Continuous-Integration section in this workflow file

Describe alternatives you've considered

  • N/A

Approach to be followed (optional)

  • N/A

Additional context

  • N/A

Potential internship candidates

@Tarunmeena0901
Copy link
Contributor

@palisadoes i would like to work on this issue

Copy link

github-actions bot commented Jan 6, 2024

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.

@github-actions github-actions bot added the no-issue-activity No issue activity label Jan 6, 2024
@Tarunmeena0901
Copy link
Contributor

this issue is fixed kindly close

@Tarunmeena0901 Tarunmeena0901 removed their assignment Jan 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants