When creating a pull request to add a new feature or alter an existing one,
there are some important elements to include to help our team review and process it more efficiently.
Make sure the title is descriptive of what the PR includes. Don't mention issue names/numbers; save that for the description.
Automating push to PyPi.
List the names of those who contributed to the project.
@VitalJoseph , @KellerLiptrap , @MilesF25 , @Poiuy7312, @boulais01
When creating a pull request to add a new feature or alter an existing one, there are some important elements to include to help our team review and process it more efficiently.
Make sure the title is descriptive of what the PR includes. Don't mention issue names/numbers; save that for the description. Automating push to PyPi.
List the names of those who contributed to the project. @VitalJoseph , @KellerLiptrap , @MilesF25 , @Poiuy7312, @boulais01
Link the issue the pull request is meant to fix/resolve. https://github.com/AstuteSource/chasten/issues/80
Describe the contents and goal of the pull request.
The goal is to be able to automate pushing to PyPi
Mark as a draft until it is ready to begin the reviewing process, then tag our Lead Software Architect, Lauren Nevill, our Principal Software Engineer, Bergas Batara, and our Founding Engineer, Gregory Kapfhammer when you mark it as ready for review.