Skip to content
This repository has been archived by the owner on Oct 10, 2024. It is now read-only.

Should we be telling people to use temporary branches and git amend? #61

Open
odscjames opened this issue May 3, 2018 · 3 comments
Open

Comments

@odscjames
Copy link
Contributor

https://github.com/OpenDataServices/developer-docs/blob/master/tools/git.md#temporary-branches

In general having temporary commits on temporary branches is better than using git stash. ... they can also be pushed to the server. .... If you have a temporary commit you can update it using git commit --amend -a --date="date``

If you push to a remote, git amend and then try and push again that's not great? Maybe take advice out about commit --amend?

(Also maybe tell people to delete temporary branches from GitHub when done?)

@BibianaC
Copy link
Member

BibianaC commented May 4, 2018

Temporary branches with temporary commits, does this mean to always work in branches instead of master?
+1 on deleting them once done.

@odscjames
Copy link
Contributor Author

Yes, the first section of https://github.com/OpenDataServices/developer-docs/blob/master/tools/git.md specifies feature branches. (Actually it specifies "most", we should maybe clarify that later!)

@BibianaC
Copy link
Member

BibianaC commented May 4, 2018

It would be good to clarify this 'must'. Specify what is allowed not to be in a branch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants