-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump github.com/daixiang0/gci from 0.2.4 to 0.2.7 #1521
build(deps): bump github.com/daixiang0/gci from 0.2.4 to 0.2.7 #1521
Conversation
8c7c23e
to
8bb6d86
Compare
@daixiang0 the error seems related to version changes, not sure if it's breaking change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While the change is ok, but test failure might be related to version change. We might need to do slight adjustment.
let me check it. |
8bb6d86
to
2ba916b
Compare
Bumps [github.com/daixiang0/gci](https://github.com/daixiang0/gci) from 0.2.4 to 0.2.5. - [Release notes](https://github.com/daixiang0/gci/releases) - [Commits](daixiang0/gci@v0.2.4...v0.2.5) Signed-off-by: dependabot[bot] <support@github.com>
2ba916b
to
b365af4
Compare
The tags v0.2.2, v0.2.3, v0.2.4 are on dangling commits: the commits are neither on the master branch nor on any other branch I think that the master branch has been push forced. tags commits$ git show-ref --tags
e4abc2084b7411538e8db74cebabe6aa7c72db22 refs/tags/v0.1
66f1df783cb2a34683b8b8b9d158ef42240f0003 refs/tags/v0.2
1a47373a044d81e018e9dcae476a4c2402466c7d refs/tags/v0.2.1
a5f5d21eae6a166bae1457dcba44f4674acb002a refs/tags/v0.2.2
d625c55f0e9b970038f12155479831555a817f78 refs/tags/v0.2.3
c177722c22ed950e3f367331f2b9486421b6f070 refs/tags/v0.2.3.1
d625c55f0e9b970038f12155479831555a817f78 refs/tags/v0.2.4
4ad32334d5f2f22af98acd6b44a1e1b3f0b5ca38 refs/tags/v0.2.5 $ git log --oneline --decorate --tags --no-walk
4ad3233 (HEAD -> master, tag: v0.2.5, origin/master, origin/HEAD) allow non-URL local package names (#22)
d625c55 (tag: v0.2.4, tag: v0.2.3) Refactor gci.Run
a5f5d21 (tag: v0.2.2) remove duplicate blank in comment
c177722 (tag: v0.2.3.1) Remove extra space
1a47373 (tag: v0.2.1) Fix -d option cannot work
66f1df7 (tag: v0.2) Update README
e4abc20 (tag: v0.1) Add linebreak before comment line, same as goimport all commits from all the branches$ git log --oneline --decorate --graph --branches
* 4ad3233 (HEAD -> master, tag: v0.2.5, origin/master, origin/HEAD) allow non-URL local package names (#22)
* c177722 (tag: v0.2.3.1) Remove extra space
* 1a47373 (tag: v0.2.1) Fix -d option cannot work
* 0d8d190 Fix panic when comment occur in the last line
* 66f1df7 (tag: v0.2) Update README
* 106b42d refactor and implement go/analyzer
* e4abc20 (tag: v0.1) Add linebreak before comment line, same as goimport
* e0e26a3 Refactor and add testcase
* beed208 Update README
* dccec63 implement gci
* 2fa5e49 Update readme
* 05aafe0 Initial commit I created a branch dangling commits$ git log --oneline --decorate --graph --branches
* 4ad3233 (HEAD -> master, tag: v0.2.5, origin/master, origin/HEAD) allow non-URL local package names (#22)
* c177722 (tag: v0.2.3.1) Remove extra space
| * d625c55 (tag: v0.2.4, tag: v0.2.3, ghost) Refactor gci.Run
| * 6a40cd1 Remove extra space
| * a5f5d21 (tag: v0.2.2) remove duplicate blank in comment
| * 2c513d1 fix wrong exit code
|/
* 1a47373 (tag: v0.2.1) Fix -d option cannot work
* 0d8d190 Fix panic when comment occur in the last line
* 66f1df7 (tag: v0.2) Update README
* 106b42d refactor and implement go/analyzer
* e4abc20 (tag: v0.1) Add linebreak before comment line, same as goimport
* e0e26a3 Refactor and add testcase
* beed208 Update README
* dccec63 implement gci
* 2fa5e49 Update readme
* 05aafe0 Initial commit
|
@daixiang0 I think that you have to reconcile the history, the following commands will catch the dangling commits: git fetch
git checkout master
git pull origin master
git branch ghost v0.2.4
git merge ghost -m "chore: catch dangling commits"
git branch -D ghost
git push origin master After that, you have to create a new release (v0.2.6). Note: you don't have to push force. You just have to copy-paste my commands. |
@ldez done. @dependbot rebase |
@dependabot rebase |
Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
There is a regression in v0.2.5 and v0.2.6 I created a fix: daixiang0/gci#27 |
@daixiang0 could you create a v0.2.7? |
I have released v0.2.7 |
@sayboras could you take another look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 💯
Bumps github.com/daixiang0/gci from 0.2.4 to 0.2.7.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually