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

Update CONTRIBUTING.md to match PR guidelines #2424

Open
wants to merge 2 commits into
base: release-1.2
Choose a base branch
from

Conversation

acarbonetto
Copy link
Contributor

Issue link

This Pull Request is linked to issue (URL): #2422
Follows: #2411

Checklist

Before submitting the PR make sure the following are checked:

  • [ x ] This Pull Request is related to one issue.
  • [ x ] Commit message has a detailed description of what changed and why.
  • N/A Tests are added or updated.
  • N/A CHANGELOG.md and documentation files are updated.
  • [ x ] Destination branch is correct - main or release
  • [ x ] Commits will be squashed upon merging.

@acarbonetto acarbonetto requested a review from a team as a code owner October 10, 2024 18:30
@acarbonetto acarbonetto changed the base branch from main to release-1.1 October 10, 2024 18:31
@acarbonetto acarbonetto changed the base branch from release-1.1 to release-1.2 October 10, 2024 18:31
@acarbonetto acarbonetto force-pushed the docs/update_release_process branch from fe64eb8 to 3003fe1 Compare October 10, 2024 21:59
@acarbonetto acarbonetto force-pushed the docs/update_release_process branch from 3003fe1 to 6c65658 Compare October 11, 2024 05:08
@acarbonetto acarbonetto self-assigned this Oct 11, 2024
@acarbonetto acarbonetto added the docs Documentation label Oct 11, 2024
Copy link
Collaborator

@ikolomi ikolomi left a comment

Choose a reason for hiding this comment

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

Please do not change pull_request_template.md

@acarbonetto
Copy link
Contributor Author

Please do not change pull_request_template.md

I'm not sure why you are saying this. Is this because we should not be backporting changes to main? Please elaborate.

This is a crucial reminder now that we have added version/release branches and these changes are blocking development.

@acarbonetto
Copy link
Contributor Author

Will remove pr changes, and have raised #2441 to discuss way forward and make sure we don't forget to backport changes from release branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants