-
Notifications
You must be signed in to change notification settings - Fork 99
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
Update PULL_REQUEST_TEMPLATE.md #1067
Conversation
Updated the PR template to put a reminder, so that when we do new version releases we notify the comms team about it in advance. Signed-off-by: Adi Seredinschi <adi@informal.systems>
.github/PULL_REQUEST_TEMPLATE.md
Outdated
@@ -26,3 +26,5 @@ ______ | |||
|
|||
- [ ] Reviewed `Files changed` in the GitHub PR explorer. | |||
- [ ] Manually tested (in case integration/unit/mock tests are absent). | |||
- [ ] __If new version release__: Notify the comms team about the pending release and [prepare a message](https://www.notion.so/informalsystems/Communications-pipeline-b8c0eeb71dc24203a048fa6ccf189e1a?pvs=4) to announce it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears to be a link to a restricted page. Should it stay public?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it should be a private page, shared with Andrea, then he will manage making the public communications out of that content in that private page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant, should the link address be visible to the public - even though not everyone can open it and read its content ? 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appreciate adding this @adizere 🙏
I've the same comment as Rano's. I'd suggest not pointing to a private page since it'll be in all PRs. What about adding it as an initial step into the RELEASES.md?
Does this fix it @rnbguy @Farhad-Shabani ? d8ca5c6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adizere thanks very much for the PR 🙏
I suggested some changes. I will wait for Farhad to give the final approval.
Co-authored-by: Rano | Ranadeep <ranadeep@informal.systems> Signed-off-by: Farhad Shabani <Farhad.Shabani@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
* Update PULL_REQUEST_TEMPLATE.md Updated the PR template to put a reminder, so that when we do new version releases we notify the comms team about it in advance. Signed-off-by: Adi Seredinschi <adi@informal.systems> * using releases.md instead of PR template * Apply suggestions from code review Co-authored-by: Rano | Ranadeep <ranadeep@informal.systems> Signed-off-by: Farhad Shabani <Farhad.Shabani@gmail.com> --------- Signed-off-by: Adi Seredinschi <adi@informal.systems> Signed-off-by: Farhad Shabani <Farhad.Shabani@gmail.com> Co-authored-by: Farhad Shabani <Farhad.Shabani@gmail.com> Co-authored-by: Rano | Ranadeep <ranadeep@informal.systems>
Updated the PR template to put a reminder, so that when we do new version releases we notify the comms team about it in advance.
PR author checklist:
Reviewer checklist:
Files changed
in the GitHub PR explorer.