I just completed the following:
git add * && git commit -m "message" && git push
However, sometimes I see this issue and am confused as to what it means. Sometimes it's for files I delete and sometimes it's for changes that have not merged correctly.
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add/rm <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
no changes added to commit (use "git add" and/or "git commit -a")
Quoted from this site: https://www.atlassian.com/git/tutorials/saving-changes/git-add
"The staging area is one of Git's more unique features, and it can take some time to wrap your head around it if you’re coming from an SVN (or even a Mercurial) background. It helps to think of it as a buffer between the working directory and the project history.
Instead of committing all of the changes you've made since the last commit, the stage lets you group related changes into highly focused snapshots before actually committing it to the project history. This means you can make all sorts of edits to unrelated files, then go back and split them up into logical commits by adding related changes to the stage and commit them piece-by-piece. As in any revision control system, it’s important to create atomic commits so that it’s easy to track down bugs and revert changes with minimal impact on the rest of the project."
So when you make a change to a file in git. The first command:
git statusI can see this:
git add myquote2.htmlto add the file to the staging area. Then I run
git statusagain (you really don't have to do that every time but for the sake of illustration) and I see this:
Now you can see myquote2.html is in the "Changes to be committed" section which is the staging area.
Then I run
git commit myquote2.html -m 'repeated quote to show how a change moves through the process' which commits the change to the project history.
Now you can see the file is committed (um, to master in this case which is generally NOT a good idea ) and the working directory (your local folder) is clean.
Hope this helps a little. We've got some pretty good tutorials for git and Bitbucket:
To learn pull requests:
Or how to use SourceTree if you prefer an app to the command line:
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot