![]()
continuous-integration/drone/push Build is passing
Details
|
3 years ago | |
---|---|---|
Documentation/doc-images | 3 years ago | |
Sources | 3 years ago | |
.drone.yml | 3 years ago | |
.gitignore | 3 years ago | |
README.md | 3 years ago |
README.md
dice_app: the die throwing app
To use the app
TLDR: you can't really
Open the DiceApp solution and navigate to the App project. The Program.cs file has a Main()
method that can be launched. It will soon be able to load a stub. Then you will be able to play a console prototype / perform functional tests. But it isn't ready yet.
To contribute (workflow)
We are using the feature branch workflow (details here, or see the summary below)
1 - Sync with the remote
Make sure you're working with the latest version of the project
git checkout main
git fetch origin
git reset --hard origin/main
2 - Create a new branch
Give your new branch a name referring to an issue (or maybe a group of similar issues)
git checkout -b new-feature
Regularly, you might want to get all the new code from your main branch, to work with an up-to-date codebase:
git pull --rebase origin main
3 - Code
🔥🧑💻🐛🔥............✅
4 - Save your changes to your new branch
For a refresher, see details about add
, commit
, push
, etc. here
It should involve creating a corresponding feature branch on the remote repository
git push -u origin new-feature
5 - Create a Pull Request
On the repository's main page, or on your new branch's main page, look for a New Pull Request
button.
It should then allow you to merge into: ...:main
and pull from: ...:new-feature
Follow the platform's instructions, until you've made a "work in progress" (WIP) pull request. You can now assign reviewers among your colleagues. They will get familiar with your new code -- and will either accept the branch as it is, or help you arrange it.