Follow the git bug bridge configure wizard as per below. Check the error at the end. A breaking change at github?

This is a real token from github that I have expired, just so you can see the format. Other personal data has been redacted.

git bug bridge configure
[1]: github
[2]: gitlab
[3]: jira
[4]: launchpad-preview
target: 1
name [default]: 

Detected projects:
[1]: github.com/my-user/private-project

[0]: Another project

Select option: 1
Github login: my-user

[1]: enter my token
[2]: interactive token creation

Select option: 1

You can generate a new token by visiting https://github.com/settings/tokens.
Choose 'Generate new token' and set the necessary access scope for your repository.

The access scope depend on the type of repository.
Public:
  - 'public_repo': to be able to read public repositories
Private:
  - 'repo'       : to be able to read private repositories

Enter token: ghp_<!-- REDACTED -->
token has incorrect format

edited by @sudoforge to remove a token; whether or not this was active is unknown, but its existence triggers a security alert.

gavin-shaw (gavin-shaw) changed the title from Github Bridge - Manual Token - "token has wrong format" to Github Bridge - Manual Token - "token has wrong format" 4 years ago

For me using the latest version in master and using "interactive token creation" worked.

Confirmed manual token is also working on master, thank you @mohe2015 . I think we should leave this open for others until master hits the package managers?

I am on mac with brew.

For those landing here, check the releases page first to see if there is a release after 2021-11-28. If not, follow instructions under Installation > Compile from git (unstable) in the README.md.

git clone git@github.com:MichaelMure/git-bug.git
make install
export PATH=$PATH:$(go env GOROOT)/bin:$(go env GOPATH)/bin

Tested and working on Mac M1. Make sure you have latest version of go installed.

I have this problem too, with the git-bug packaged in nixpkgs.

Please produce a numbered release with this bug, otherwise distributions won't pick it up.

IMHO this project is significantly less useful without the github bridge. Unbreaking that would seem worthy of a release, no?

getting same with gitlab, tried to setup this morning, won't accept the token. checked and re-checked. expired one tried a new one. Same issue.

I believe the last release fix that issue. Feel free to reopen if not.

Michael Muré (MichaelMure) closed the bug 3 years ago

Still seems to be broken for me, but the binaries for 0.8 still say version 0.7.2, so I'm not sure what is going on.

Michael Muré (MichaelMure) opened the bug 3 years ago

@jarbus I think that somehow you do have a binary for 0.7.2. I just checked the pre-build binary of the v0.8.0 release, they report the correct version.

... which would also explain why you still see the bug.

This is awesome, so 0.7.2 is broken because of this bug, and 0.8.0 is broken because of #934. Nice! What should one do?

github-actions (github-actions) added label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 11 months ago

github-actions (github-actions) removed label lifecycle/stale 11 months ago

sudoforge removed label lifecycle/dormant 7 months ago