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

Permission denied #1

Closed
lambtron opened this issue Dec 18, 2014 · 14 comments
Closed

Permission denied #1

lambtron opened this issue Dec 18, 2014 · 14 comments

Comments

@lambtron
Copy link

Sick project, thanks for making this.

Just a heads up that I get this error when trying to commit from your script:

ERROR: Permission to gruiz17/kunstler.git denied to lambtron.

Where in your script does it look for my GitHub permissions? Maybe there can be a place where I can manually update the GitHub project to one of mine?

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

Eh? weird...I don't have it looking for GitHub permissions, I just change the author date and content date. Though it does seem like a good idea to be able to update the GitHub project to the user's own.

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

@lambtron do you mean it happens after it says 'going through commits now...'?

@lambtron
Copy link
Author

Yeah precisely! It happens right after going through commits now.

Thanks for looking into it!

@lambtron
Copy link
Author

Example:

committing! on
2014-01-06 00:00:12 -0500
committing! on
2014-01-06 00:00:13 -0500
committing! on
2014-01-06 00:00:14 -0500
committing! on
2014-01-06 00:00:15 -0500
committing! on
2014-01-06 00:00:16 -0500
committing! on
2014-01-06 00:00:17 -0500
committing! on
2014-01-06 00:00:18 -0500
committing! on
2014-01-06 00:00:19 -0500
committing! on
2014-01-06 00:00:20 -0500
committing! on
2014-01-06 00:00:21 -0500
committing! on
2014-01-06 00:00:22 -0500
committing! on
2014-01-06 00:00:23 -0500
committing! on
2014-01-06 00:00:24 -0500
ERROR: Permission to gruiz17/kunstler.git denied to lambtron.
fatal: Could not read from remote repository.

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

@lambtron "Could not read from remote repository"...hmm, I do have kunstler.sh set to automatically push to 'master' (as in MY master branch on GitHub) so if you cloned it that part of the script would throw a permissions error. Should I just take git push origin master out of the script?

@lambtron
Copy link
Author

Oh i see, that makes sense; thats why you suggested to fork the repo. I can just change the git remote in that repo to a dummy project that I own and it should work. Let me try that.

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

Wait, I think I'm dumb lol, I don't think commits to forked projects actually show up...hmm, now I have to figure out another way to actually make this accessible to other users huh.

Thanks for bringing this up!

@lambtron
Copy link
Author

Oh haha. I was just about to comment saying that it worked, but the commits didn't show up. No worries! I look forward to using this.

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

Haha, thanks!

Hold on, give me 4 minutes, I think I have a really hacky solution. LOL

@lambtron
Copy link
Author

Sweet no worries.

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

Ah! Got one.

  1. Make a new repo in your own profile called "kunstler"
  2. Clone my repo
  3. cd into my repo
  4. In command line type git remote set-url origin https://github.com/[username]/kunstler.git

And when you do git push origin master it will work. Hacky as hell and but it sort of works.

Or you could send me pull requests and I could merge them into my own repo after you forked them but that means destroying my own art LOL

@lambtron
Copy link
Author

Haha ok yeah i was thinking along the same lines.

I actually went ahead and did that (see it here: https://github.com/lambtron/gruiz17-kunstler). For some reason, Jan 6th 2014 commits show up as Jan 5th in contributions, even though when you click through it, it shows the commits were done Jan 6th.

Weird??

@lambtron
Copy link
Author

@gruiz17
Copy link
Owner

gruiz17 commented Dec 18, 2014

whaaaat? Weird. I'll look into it later.

Actually I'll close down this current issue. This discussion's better for another issue.

@gruiz17 gruiz17 closed this as completed Dec 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants