-
Notifications
You must be signed in to change notification settings - Fork 6
Development Guidelines
To keep things straightforward, here's how we handle development.
- Fork the repo
- We don't want to have the hygiene of the main repo be dependent on everyone remembering to delete their remote branches, so please have a fork (that you keep synchronized with master here).
- Work in a feature branch
- Keep the names professional, and try and make sure they have some relationship to what it is you're working on. Try and branch off of a clean copy of upstream's master
git checkout master git fetch [upstream remote name] git reset --hard [upstream remote name]/master ``` 3. Submit new features via a pull request to master - Travis is currently running a PEP8 linter against every pull request. If your code does not pass PEP8, it will not get merged! Note: you can safely ignore line-length errors (E501), as Travis should be configured to ignore those, and we don't really care about them. 4. Any other developer on the team can merge a pull request, but only after they've pulled the changes and tried them out and Travis has marked the build as "Passed".
We work in one week sprints, from Tuesday meeting to Tuesday meeting. Tasks for the sprint will be assigned via GitHub, and kept up to date in Confluence.