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

Collaborator Can't Push Changes to Repository [Access Denied] #6

Open
PolyTyme opened this issue Apr 3, 2024 · 5 comments
Open

Collaborator Can't Push Changes to Repository [Access Denied] #6

PolyTyme opened this issue Apr 3, 2024 · 5 comments

Comments

@PolyTyme
Copy link

PolyTyme commented Apr 3, 2024

I have a collaborator that I want to give the ability to receive and send changes to the git repo from Obsidian with the Github Sync plugin. Everything works in CLI, until we get to the point where the plugin changes the remote url to the "https://Username.gitKey@github.com/Owner/Name.git" format. When that happens, the system gives the error that access is denied to the collaborator.

I believe that their key is correct with all permissions, the repo has no restrictions to collaborators, and they supposedly have push and pull access.

@Bistutu
Copy link

Bistutu commented Jun 10, 2024

I also encountered this issue where 'https' was repeated twice. Therefore, I resolved it by removing the 'https' prefix in the configuration center.

image image

@sefatanam
Copy link

Hello @Bistutu

Some common thing need to check before sync,
Assume that you already created git repo in github then don't forget to add these lines into .gitignore because it contain your github's personal access token which refuse by Github from exposing publicly.

.obsidian/plugins/github-sync/data.json // this is enough but you can also add the bellow or use pattern
.obsidian/plugins/github-sync/main.js
.obsidian/plugins/github-sync/manifest.json
.obsidian/plugins/github-sync/styles.css

basically that's it.

@kevinmkchin
Copy link
Owner

@PolyTyme let me know if your issue persists or if I can close this issue. The package has been updated for a simpler setup process which may alleviate some of your issues.

@PolyTyme
Copy link
Author

PolyTyme commented Oct 2, 2024

@PolyTyme let me know if your issue persists or if I can close this issue. The package has been updated for a simpler setup process which may alleviate some of your issues.

This issue is still persisting, but I will look into the new updated setup to see if that works better.

@jgolta
Copy link

jgolta commented Dec 24, 2024

same problem here

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

5 participants