Skip to content

Conversation

@person198319
Copy link


A good PR should include the following parts:

  • A clear title
  • A meaningful message for PR, as well as its commits
  • from your specific branch (not master) merging to TA's HW branch (not master, again)
  • excluding any irrelevant files, such as binaries, text files, or dot files
  • passing tests/CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants