Setting up git: Difference between revisions
Jump to navigation
Jump to search
m
Links to coding standards page
imported>Cheridan |
imported>Cheridan m (Links to coding standards page) |
||
| Line 88: | Line 88: | ||
* A commit is confirmed change of the files in your repo, it's how you make changes permanently to the files in your repo, so try not to commit without making sure it works (though subsequent commits can fix it). | * A commit is confirmed change of the files in your repo, it's how you make changes permanently to the files in your repo, so try not to commit without making sure it works (though subsequent commits can fix it). | ||
* As said before, you should use different branches to separate your commits/changes. Don't commit to master. It should be clean, so you can fall back on it if needed. | * As said before, you should use different branches to separate your commits/changes. Don't commit to master. It should be clean, so you can fall back on it if needed. | ||
* To make your commits, you need to edit the files using BYOND's inbult editing tools. | * To make your commits, you need to edit the files using BYOND's inbult editing tools. Make sure to [[Coding Standards|follow coding standards]] when making your changes! When you're finished, right click the folder you're working with and choose '''Git Commit -> "[Your Branch Name]"''' (Example: Git Commit -> "My_First_Branch") | ||
* You can then select only the files you want to be committed by ticking or unticking them. You should also write a detailed commit summary, detailing what happened in that commit. | * You can then select only the files you want to be committed by ticking or unticking them. You should also write a detailed commit summary, detailing what happened in that commit. | ||
* Click '''Ok''' and the commit will be committed to your local repo! | * Click '''Ok''' and the commit will be committed to your local repo! | ||