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

doc: Add GitHub issue template for releasing Conduit #1947

Merged
merged 3 commits into from
Nov 8, 2024

Conversation

raulb
Copy link
Member

@raulb raulb commented Nov 8, 2024

Description

Every time we have to do a Conduit release, we have to go through this document, which contains all the necessary information. This however, often involves having to follow through a checklist elsewhere. The idea with this issue template is that we could create an issue for every future release, and follow through so we can also document the process and maintain up to date.

I'll still want to update the releases document to refer to this template so we don't have the same information in two places.

Quick checks

  • I have followed the Code Guidelines.
  • There is no other pull request for the same update/change.
  • I have written unit tests.
  • I have made sure that the PR is of reasonable size and can be easily reviewed.

@raulb raulb self-assigned this Nov 8, 2024
@raulb raulb marked this pull request as ready for review November 8, 2024 10:00
@raulb raulb requested a review from a team as a code owner November 8, 2024 10:00
Copy link
Contributor

@hariso hariso left a comment

Choose a reason for hiding this comment

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

Very nice! 🚀

@raulb raulb enabled auto-merge (squash) November 8, 2024 10:10
@raulb raulb merged commit 0c74ada into main Nov 8, 2024
4 checks passed
@raulb raulb deleted the add-release-template branch November 8, 2024 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants