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

Need elevated repository rights, please #1

Open
BionicCode opened this issue Dec 26, 2023 · 20 comments
Open

Need elevated repository rights, please #1

BionicCode opened this issue Dec 26, 2023 · 20 comments

Comments

@BionicCode
Copy link
Collaborator

Hey, how are you doing? Did you had a nice Christmas?

I was just trying to create a pull request. I wanted to push a new branch but had to realize that I don't own the rights to do so.
Would you mind allowing me to create pull requests?

Thanks!
Brian

@MaroisConsulting
Copy link
Owner

MaroisConsulting commented Dec 27, 2023

@BionicCode I removed branch protections from the repository. Please try again

@BionicCode
Copy link
Collaborator Author

BionicCode commented Dec 27, 2023

@MaroisConsulting Thanks. But I still can't create/push new branches. But I have implemented the theming example in a dedicated branch.

To enable me to push my commits, please create the following branch for me: "Example_ThemeManager" .

Thanks

@MaroisConsulting
Copy link
Owner

@BionicCode Done.

@BionicCode
Copy link
Collaborator Author

Thanks for your patience. The branch is there. I was able to pull and merge it. But I still don't have the permission to push.

"Failed to push to the remote repository. See the Output window for more details.
Writing commit graph for 'MyCustomControl'
Pushing Example_ThemeManager
Remote: Permission to MaroisConsulting/MyCustomControl.git denied to BionicCode.
Error encountered while pushing to the remote repository: Git failed with a fatal error.
Git failed with a fatal error.
unable to access 'https://github.com/MaroisConsulting/MyCustomControl.git/': The requested URL returned error: 403

Failed to push to the remote repository. See the Output window for more details."

@MaroisConsulting
Copy link
Owner

MaroisConsulting commented Dec 27, 2023

Why don't you send me yout email address to [email protected], and I'll add you with permissions?

@BionicCode
Copy link
Collaborator Author

You find when you click on my account, It's public: [email protected]

@MaroisConsulting
Copy link
Owner

@BionicCode OK, I added you as a collborator

@BionicCode
Copy link
Collaborator Author

Ok, nice. Thanks. But still nothing has changed for me. Collaborator does not automatically receive special permissions. This depends on how the repo is configured.
Sorry to worry you. I can create a new repo and invite you if that makes it easier for you.

@MaroisConsulting
Copy link
Owner

@BionicCode Sure go ahead

@BionicCode
Copy link
Collaborator Author

Have you created rule sets for your repo?

@MaroisConsulting
Copy link
Owner

@BionicCode No, I just created a public repo

@BionicCode
Copy link
Collaborator Author

And as a collaborator you explicitly allowed me to push to the repo?

@BionicCode
Copy link
Collaborator Author

Because "public" means only visible without further legitimations.

@MaroisConsulting
Copy link
Owner

@BionicCode The repo says it's still 'Pending Invite' to you. Did you accept the invite?

@BionicCode
Copy link
Collaborator Author

Ahh ok. That's on me! Sorry. The invitations ended up in my spam folder (for some reason)

@BionicCode
Copy link
Collaborator Author

Here we go. Finally. Thanks Kevin. I'm Brian by the way...

@MaroisConsulting
Copy link
Owner

@BionicCode Pleasure to meet you!

@BionicCode
Copy link
Collaborator Author

Yes, my pleasure!

Let me know if I can do anything.

@MaroisConsulting
Copy link
Owner

@BionicCode Great! Thanks. I have the code and will review it.

Thanks again for all your help.

@BionicCode
Copy link
Collaborator Author

I'm happy I could help. I hope you find the example useful.
You can run the application to see the effects.
To understand the code better you should read the Theme_Resources_Naming_Conventions.txt and of course the comments.

I also hope you find the Review result.txt any useful.

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