-
Notifications
You must be signed in to change notification settings - Fork 83
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
Doc fragment check on PR with gh actions #186
Labels
Comments
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
rrey
added a commit
that referenced
this issue
May 1, 2022
Limitations: - The comment asking for the fragment will be posted at each push on the PR until the fragment is present. Closes:: #186
rrey
added a commit
that referenced
this issue
Jun 25, 2022
Limitations: - The comment asking for the fragment will be posted at each push on the PR until the fragment is present. Closes:: #186
Resolved by #247 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
Collections requires that semver is followed and that we have clean release message listing all changes by severity.
Contributors often forget to include the doc fragment in their PR, we could automatically have the PR reviewed to "Request changes" by a bot that would check that the PR contains a doc fragment.
ISSUE TYPE
COMPONENT NAME
CI
The text was updated successfully, but these errors were encountered: