commits
Here are 136 public repositories matching this topic...
-
Updated
May 11, 2020 - Shell
-
Updated
Oct 7, 2018 - Ruby
-
Updated
Mar 22, 2020 - Python
$ git commit
.git/hooks/prepare-commit-msg: line 43: conditional binary operator expected
.git/hooks/prepare-commit-msg: line 43: syntax error near `=~'
.git/hooks/prepare-commit-msg: line 43: ` if [[ "${IGNORED[*]}" =~ "${filename}" || "${IGNORED[*]}" =~ "${extension}" ]]; then'
$ cd ../commit-comments/
$ git log | head -n 1
commit a916600e8cc2b0cb0f6da2533d616da3ddca5f68
$ /bin/bash --ver
I would really appreciate seeing this limitation documented a little further.
Specifically I would like to understand the issue with merge commits and know if there is a migration path from a codebase with a long history of these to one which would be ready to use fbshipit.
-
Updated
Mar 6, 2020
Running these commands
git clone https://github.com/paramiko/paramiko.git
cd paramiko
git checkout -b my2.2.3 2.2.3
git tag to-backport 56c96a65
git deps -r -e my2.2.3
I get
Fatal: -L invalid line number: 0
Traceback (most recent call last):
File "/usr/bin/git-deps", line 10, in <module>
sys.exit(run())
File "/usr/lib/python3.6/site-packages/git_deps/cli.py
-
Updated
May 29, 2020 - Go
-
Updated
Aug 1, 2019 - Shell
When releasing the last mochify version I forgot to add a new contributor to package.json and had to do that manually afterwards.
Should changes do that (which probably wouldn't be too hard to do as everything is already there)? Or should its scope stay limited to the CHANGELOG?
Rather than requiring regex to delete comments, it would be great if this would automatically check if the comment exists, and if so, do not add a further comment.
For example, when setting up a PR review environment, we don't want it to constantly post the URL to the PR. We only need it done once.
-
Updated
Jun 5, 2019 - Python
From @sfabrizio on September 12, 2016 17:24
We have some new staff that we are not showing in the demo git yet.
Copied from original issue: labs-js/turbo-commit#36
-
Updated
Jun 24, 2019
-
Updated
Jun 13, 2016 - JavaScript
-
Updated
Jun 29, 2017 - JavaScript
-
Updated
May 8, 2017 - Java
-
Updated
Feb 12, 2019 - JavaScript
-
Updated
May 15, 2020 - Shell
Improve this page
Add a description, image, and links to the commits topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the commits topic, visit your repo's landing page and select "manage topics."
Hello @carloscuesta and @grissius😎 !
The CONTRIBUTING.md lacks a step currently in order to add a new emoji.
If one follows the written steps we get build:failed on TravisCI when making a Pull Request: carloscuesta/gitmoji#377
I was only able to find the missing step by looking at the last successful run on a Pull Request: https://github.com/carloscuesta/git