Put the following in your build.gradle file for the project. There’s no need to modify the manifest directly: Google provided the necessary hooks into their configuration. def getVersionCode = { -> try { def code = new ByteArrayOutputStream() exec { commandLine ‘git’, ‘tag’, ‘–list’ standardOutput = code } return code.toString().split(“\n”).size() } catch (ignored) { return … Read more
It’s now possible to try the Heroku feature Roberto wrote about in his answer, without contacting Heroku. It’s called Heroku Labs: Dyno Metadata and you can enable it by heroku labs:enable runtime-dyno-metadata -a <app name> and then the information is available (on the next deploy) as environment variables: ~ $ env HEROKU_APP_ID: 9daa2797-e49b-4624-932f-ec3f9688e3da HEROKU_APP_NAME: example-app … Read more
Edit: As of Git version 1.8.4, but with an important side bug fixed in Git version 2.0.1, git rebase now has –autostash. You can configure git rebase to use –autostash by default as well, with git config –global rebase.autoStash true. Please note the following sentence from the documentation: However, use with care: the final stash … Read more
The ProGit book has an interesting section on Removing Object. It does end with this: Your history no longer contains a reference to that file. However, your reflog and a new set of refs that Git added when you did the filter-branch under .git/refs/original still do, so you have to remove them and then repack … Read more
If you know the ref, then git show <MERGE_COMMIT> will show you the resolution done (if any) for the merge commit. For log, use git log -p -c or git log -p –cc. From the manpage of git log: -c With this option, diff output for a merge commit shows the differences from each of … Read more
“C:\Program Files (x86)\Git\bin\sh.exe” –login -i -c “git archive master | tar -x -C $0” “%~1”
As I explain in this answer to Delete or remove all history, commits, and branches from a remote Git repo?, you can also achieve the same thing as Ceilingfish’s answer (i.e. delete all references/branches/tags in the remote repo) by doing the following: Create new empty repo with initial commit: mkdir new cd new echo “This … Read more
git version 1.8.4 added an –author-date-order argument to git log; according to the release notes, “the output is topologically sorted and commits in parallel histories are shown intermixed together based on the author timestamp.”
These two files contains absolute submodule path: {submodule}/.git .git/modules/{submodule}/config So, if you moved the repo, the absolute path in these two files are not valid, and cause the ‘not a git repository’ error. Just fix these files manually.