Skip to content
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

Error on UPDATE from fork #10

Closed
shaikatz opened this issue Feb 14, 2018 · 5 comments
Closed

Error on UPDATE from fork #10

shaikatz opened this issue Feb 14, 2018 · 5 comments

Comments

@shaikatz
Copy link

shaikatz commented Feb 14, 2018

Sorry for spamming you with issues today but I've gathered them from few days of usage and found a time to report them just now.

When the bot trying to update PR that is coming from a fork I'm getting this message:

2018/02/14 16:25:44 Find PR #315, updated at 2018-02-14 16:15:41 +0000 UTC
2018/02/14 16:25:46 Merge Base Commit: 08fe25e09879dc64aec30153f833f8bc791b1332
2018/02/14 16:25:46 Behind By: 1
2018/02/14 16:25:46 PR #315: UPDATE
2018/02/14 16:25:46 Add labels: [status/4-merge-in-progress]. Dry run: false
2018/02/14 16:25:46 Base branch:  master - Fork branch:  branch-name
2018/02/14 16:25:46 /tmp/myrmica-lobicornis081067040
2018/02/14 16:25:46 git clone https://TRUNCATED@github.com/ForkName/RepoName.git --branch branch-name .
2018/02/14 16:27:55 git remote add upstream https://github.com/OwnerName/RepoName.git
2018/02/14 16:27:55 git fetch --no-tags upstream master
2018/02/14 16:27:56 fatal: could not read Username for 'https://github.com': No such device or address
2018/02/14 16:27:56 Add labels: [bot/need-human-merge]. Dry run: false

I've supplied --git-email and --git-name args.

@ldez
Copy link
Contributor

ldez commented Feb 15, 2018

Are you using the bot on a private repository?

@shaikatz
Copy link
Author

Are you using the bot on a private repository?

Yes

@ldez
Copy link
Contributor

ldez commented Feb 18, 2018

For now, the bot use only public address (e.g. no authentication) for the forks.

An option should be created to manage this case.

@ldez
Copy link
Contributor

ldez commented Feb 18, 2018

I have a solution to manage this automatically. A PR coming soon.

@shaikatz
Copy link
Author

Thanks @ldez !

@ldez ldez closed this as completed in #11 Feb 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants