tyler.durden/dashy
1
0
Fork 0
mirror of https://github.com/Lissy93/dashy.git synced 2025-07-22 21:25:00 +02:00
Code Issues Packages Projects Releases Wiki Activity

📝 Updates development docs

Browse Source
This commit is contained in:
Alicia Sykes 2021-10-03 21:44:42 +01:00
parent 27d52c0635
commit 06155692de
2 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/contributing.md
View File

@ -111,5 +111,5 @@ For a full list of Dashy's contributors, see the [Credits Page](/docs/credits.md
### Star-Gazers Over Time ### Star-Gazers Over Time
![Stargazers](https://starchart.cc/Lissy93/dashy.svg) [![Stargazers](https://starchart.cc/Lissy93/dashy.svg)](https://seladb.github.io/StarTrack-js/#/preload?r=Lissy93,dashy)

12
docs/developing.md
View File

@ -84,11 +84,13 @@ You can set the environment using the `NODE_ENV` variable. By default, the corre
### Git Flow ### Git Flow
Like most Git repos, we are following the [Github Flow](https://guides.github.com/introduction/flow) standard. Like most Git repos, we are following the [Github Flow](https://guides.github.com/introduction/flow) standard.
1. Create a branch (or fork if you don'd have write acces) 1. Create a branch (or fork if you don'd have write access)
2. Code some awesome stuff, then add and commit your changes 2. Code some awesome stuff 🧑‍💻
3. Create a Pull Request, complete the checklist and ensure the build succeeds 3. Add, commit and push your changes to your branch/ fork
4. Follow up with any reviews on your code 4. Head over to GitHub and create a Pull Request
5. Merge 🎉 5. Fill in the required sections in the template, and hit submit
6. Follow up with any reviews on your code
7. Merge 🎉
### Git Branch Naming ### Git Branch Naming
The format of your branch name should be something similar to: `[TYPE]/[TICKET]_[TITLE]` The format of your branch name should be something similar to: `[TYPE]/[TICKET]_[TITLE]`