Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: split out release steps into separate doc #2615

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 16, 2025
Merged

docs: split out release steps into separate doc #2615

merged 1 commit into from
Feb 16, 2025

Conversation

rickeylev
Copy link
Collaborator

Move the steps for releasing into a separate doc.

The release steps are specific to releases, which only maintainers do. This frees up
space in the developing docs for more general tips, tricks, and guidance for others.

Along the way...

  • Remove the text about the core rules being part of Bazel
  • Put the CLA text first -- if CLAs aren't signed before code is given, it can
    result is large headaches.
  • Move some more internal dev steps out of contributing docs.

@rickeylev rickeylev requested a review from aignas as a code owner February 15, 2025 20:53
@rickeylev rickeylev enabled auto-merge February 15, 2025 20:53
aignas
aignas approved these changes Feb 16, 2025
View reviewed changes
Copy link
Collaborator

@aignas aignas left a comment

Choose a reason for hiding this comment

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

Thanks!

@rickeylev rickeylev added this pull request to the merge queue Feb 16, 2025
Merged via the queue into bazel-contrib:main with commit 0a3704d Feb 16, 2025
3 of 4 checks passed
@rickeylev rickeylev deleted the dev.docs.updates branch February 22, 2025 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@aignas aignas aignas approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rickeylev @aignas