Skip to content

chore: adding organization wide pull request template#9

Open
theproducer wants to merge 2 commits intomainfrom
new-pr-template
Open

chore: adding organization wide pull request template#9
theproducer wants to merge 2 commits intomainfrom
new-pr-template

Conversation

@theproducer
Copy link

No description provided.

@OS-pedrogustavobilro OS-pedrogustavobilro self-assigned this Feb 26, 2026
Comment on lines +23 to +26
## Versions Affected
- [ ] 7.x
- [ ] 8.x
- [ ] 9.x

Choose a reason for hiding this comment

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

Similar comment to #7 (comment)

But also, in most scenarios, community members will open PRs to main. Will people know to fill this field? Maybe if they got a bug in a specific version?

Copy link
Author

Choose a reason for hiding this comment

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

...yeah, im seeing this more as where the contributor intends for the PR to go. We can decide where it ultimately goes.

Copy link

@OS-pedrogustavobilro OS-pedrogustavobilro Feb 27, 2026

Choose a reason for hiding this comment

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

In that case, either 1. the contributor knows which branch contains his specific version (in this example 7.x, main or next), and open it there or 2. he opens it to main but checks which version(s) is the PR relevant for?

The name "Versions Affected" make it seem like it's something else. If it's a fix, it can make sense. If it's a feature, not as much?

Co-authored-by: Pedro Bilro <pedro.gustavo.bilro@outsystems.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants