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

Check files affected by task contribution Pull Requests #2644

Open
wants to merge 4 commits into
base: 2024
Choose a base branch
from

Conversation

RafDevX
Copy link
Contributor

@RafDevX RafDevX commented Oct 12, 2024

Fixes #2583

This pull request checks whether any contributions match the norm of what is expected of a task proposal/submission:

  • exactly one file changed, named README.md and in a reasonable location; and
  • PR description matches the README file (so that reviewers don't need to check both places)

ludvigch and others added 3 commits October 12, 2024 20:00
This ensures that task contribution proposal/submission content is
identical in the pull request description and the affected README.md
file, so that reviewers can have confidence that they need only check
one of them without comparing against the other.
@RafDevX RafDevX marked this pull request as ready for review October 13, 2024 12:54
Comment on lines +86 to +87
check-canvas:
name: Check proposal is compatible with previous student task registrations
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsure whether we should require our new check to pass before running the existing Python script.

Suggested change
check-canvas:
name: Check proposal is compatible with previous student task registrations
check-canvas:
name: Check proposal is compatible with previous student task registrations
needs: check-pr-description

For now, we have opted not to specify a dependency so that the jobs can run in parallel and be faster for "good PRs", which should be the majority in volume, even if "bad PRs" may suffer slightly since the last job is not aborted even if another one fails first. In any case, the scale is arguably negligible; all the checks are relatively quick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Break CI if there are more than 1 file changes
2 participants