Archive-Team
/
zfs
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 103 Wiki Activity

Initial content for page added

Peter Ashford 2018-05-28 00:24:28 -07:00
parent 8d2760e8c6
commit c7291ad1ae
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Workflow-Commit-Often.md Normal file

@ -0,0 +1,13 @@
# Commit Often
When writing complex code, it is strongly suggested that developers save their changes, and commit those changes to their local repository, on a frequent basis. In general, this means every hour or two, or when a specific milestone is hit in the development. This allows you to easily *checkpoint* your work.
Details of this process can be found in the [Commit the changes][W-commit] page.
In addition, it is suggested that the changes be pushed to your forked Github repository with the `git push` command at least every day, as a backup. Changes should also be pushed prior to running a test, in case your system crashes. This project works with kernel software. A crash while testing development software could easily cause loss of data.
For developers who want to keep their development branches clean, it might be useful to [*squash*][W-squash] commits from time to time, even before you're ready to [create a PR][W-create-PR].
[W-commit]: https://github.com/zfsonlinux/zfs/wiki/Workflow-Commit
[W-squash]: https://github.com/zfsonlinux/zfs/wiki/Workflow-Squash
[W-create-PR]: https://github.com/zfsonlinux/zfs/wiki/Workflow-Create-PR

0
Workflow/Commit-Often.md