-
Notifications
You must be signed in to change notification settings - Fork 114
Add copilot instructions and issue template tweaks #1205
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
Conversation
Co-authored-by: Toby Brain <[email protected]>
Co-authored-by: Toby Brain <[email protected]>
Co-authored-by: Toby Brain <[email protected]>
- Think about potential edge cases or scenarios that may not be covered by existing tests. | ||
- Write additional tests that would need to pass to fully validate the correctness of your solution. | ||
- Run these new tests and ensure they all pass. | ||
- Be aware that there are additional hidden tests that must also pass for the solution to be successful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are there hidden tests? Why can't we just say make sure make testacc
and make test
are successful?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It forces it to further consider edge cases 🤫
Co-authored-by: Toby Brain <[email protected]>
Co-authored-by: Toby Brain <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets give it a crack
These will be used by the copilot agent to work on issues related to this repo.