Let's learn whilst being deceptive!
Ideally, we want multiple issues & branches occurring in parallel. By the time a branch has come up with a working fix to an issue, there's probably new changes on the main branch that will need to be pulled and reconciled.
In any moment, players are being one of the following:
- Chaos Gremlin
- Demanding Capitalist
- Judgemental Rival
What Should I Do Right Now?
You do you, but here's a suggested flow that'll keep the game going
- If there are Pull Requests in need of review, be a Judgemental Rival
- If there's fewer than 2 open issues, be a Demanding Capitalist
- If there are at least 2 open issues, be a Chaos Gremlin
How to Be a Demanding Capitalist
- Create an issue asking for a particular feature, update or change
- This repo is for practicing Git flow rather than flexing our code muscles, so keep the requests reasonable.
How to Be a Chaos Gremlin
- Pick an open issue. Assign yourself to the issue.
- Create a branch and name it something relevant
- Come up with a fix for the issue in your branch.
- For extra points, simultaneously create a new problem in your code, so that a future issue can be raised in the game
- Go through the usual steps (pull from main, reconcile changes, stage, commit, push) in whatever coding environment you're using
- Create a Pull Request and request any players you'd like to review the code
How to Be a Judgemental Rival
- Review the code
- If there are changes required, either...
- Edit the commit directly (and someone else will review it)
- Request Changes via the review screen
- If an issue is revolved, close it
- Delete your own old branches if you're done with them
- Jason: I added a protection to the main branch so that it can only be merged into when someone else has reviewed a pull request
I have merged your pull request and have added some html for you to check 🙂. Happy coding!
Jason: Typos found, well played
add a little animation and styling : now the github logo is rolling!