-
Notifications
You must be signed in to change notification settings - Fork 229
Document how to skip CI in the contributing guides #908
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
Comments
Actually, do you want to just document this in MAINTENANCE.md at the current PR #906? |
Better to do one simple thing in one PR. |
One note: when we merge a PR, we should be cautious that the merge message (default to be a list of commit messages in this branch) can't contain |
Just checking, do you think it's really necessary to document this in our guide (since it's getting quite long)? Or can we just point it out to people (on a need to know basis) and close this issue? |
OK with closing the issue. |
https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/
Finally, GitHub support skipping workflows to save CI resources! Will try how it looks like in next pushes/PRs. If it works well, we should document it in the contributing guides at CONTRIBUTING.md, and even in the Pull Request template.
The text was updated successfully, but these errors were encountered: