Skip to content

Template Pull Request (Short and Descriptive Title, Usually Can Just Be Ticket Name)#27

Open
naasanov wants to merge 1 commit intomainfrom
template-pr
Open

Template Pull Request (Short and Descriptive Title, Usually Can Just Be Ticket Name)#27
naasanov wants to merge 1 commit intomainfrom
template-pr

Conversation

@naasanov
Copy link
Copy Markdown
Collaborator

High level motivation for making the changes

Changes:

  • I added this for that reason
  • And changed that for this reason
  • And deleted this cuz it sucks

It will feel a bit like you're rehashing the ticket description, but PRs should still be descriptive and its a good way to summarize your work and catch things you missed.

Closes #26

@naasanov naasanov requested a review from manyuagashe October 14, 2025 21:56
@manyuagashe
Copy link
Copy Markdown
Collaborator

Potential additions:

Write out your additions, alterations and deletions separately.

Ask further questions to Nick IN the PR if you need to (always refer to the TDD first before asking questions though)

mention if and where you may have needed code assistance from AI. This is not to grill you, we're AI-friendly (and need to be to develop and scale fast), but Nick should be aware if there's particular aspects of the code that came from AI, why you needed help, and how nick and manyu may better support you.

not merging because change is irrelevant.

@manyuagashe manyuagashe added the template PR what you should refer to when you are making your own PR's. label Oct 14, 2025
@naasanov naasanov mentioned this pull request Oct 15, 2025
@naasanov naasanov mentioned this pull request Oct 30, 2025
@naasanov naasanov mentioned this pull request Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

template PR what you should refer to when you are making your own PR's.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Template Issue

3 participants