Skip to content

Conversation

@lydiagarms
Copy link
Collaborator

Adds a template for new PRs.

@lydiagarms lydiagarms requested a review from kKahina January 8, 2026 11:14
Copy link
Contributor

@kKahina kKahina left a comment

Choose a reason for hiding this comment

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

let me know what do you think

Copy link
Contributor

Choose a reason for hiding this comment

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

as for starlight, is it good to precise and add a field for which part of the pipeline the PR touches ? circuit, orchestration,,,,? but maybe is not to important just optinal , another suggestion, you can add after ##Summary ## Related Issues

, for traceability.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think we don' need to mention what part the PR touches as a significant number of PRs touch everything, and this should be detailed in the commit messages. I will add Related Issues though.

Copy link
Contributor

@kKahina kKahina left a comment

Choose a reason for hiding this comment

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

Good!

@lydiagarms lydiagarms merged commit e2673fe into master Jan 13, 2026
4 checks passed
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.

4 participants