Require permissions to push - New contributor

[Gowrima Jayaramu <go...@gmail.com>]

Hi,

I am a new contributor and need permissions to push the changes to Github.
Please check the following message I received when I tried to push my
changes,

14:57:07.225: [zookeeper] git -c credential.helper= -c core.quotepath=false
-c log.showSignature=false push --progress --porcelain origin
refs/heads/ZOOKEEPER-4020:refs/heads/ZOOKEEPER-4020 --set-upstream
remote: Permission to apache/zookeeper.git denied to g-apache.
fatal: unable to access 'https://github.com/apache/zookeeper.git/': The
requested URL returned error: 403
14:57:32.508: [zookeeper] git -c credential.helper= -c core.quotepath=false
-c log.showSignature=false push --progress --porcelain origin
refs/heads/ZOOKEEPER-4020:refs/heads/ZOOKEEPER-4020 --set-upstream
remote: Permission to apache/zookeeper.git denied to g-apache.
fatal: unable to access 'https://github.com/apache/zookeeper.git/': The
requested URL returned error: 403

Thank you,
gowrima

Re: Require permissions to push - New contributor

[Christopher <ct...@apache.org>]

In order to have write access to the repository, you need to be voted
in as a committer by the existing ZooKeeper PMC. If you have been
voted in as a committer to Apache ZooKeeper already, and are just
trying to figure out how to get your Apache account linked to GitHub,
so you have write access to the repo, then you should go to
https://gitbox.apache.org and follow the instructions there.

For all other contributors, you must push to your fork on GitHub, and
issue a pull request to propose a change. This is recommended in most
cases, even if you were voted in as a committer on the project and
given write access, because it enables code reviews to occur before
accepting a proposed change.

You should take the following steps:

1. Create a fork on GitHub of the apache/zookeeper repository (click
the "Fork" button at https://github.com/apache/zookeeper)
2. Add a second remote for your fork to your local workspace (git
remote add <myForkName> <URLtoMyFork>)
3. Push your commits in your local working branch to your fork (git
push --set-upstream <myForkName> <myBranchName>)
4. Create a pull request from your branch to the target branch in
ZooKeeper (click "New pull request" button at
https://github.com/apache/zookeeper/pulls)

If you have any questions about each of these steps, there is a lot of
general information about how to work with multiple git remotes, how
to make pull requests, and more if you search using Google or your
preferred search engine. Here is one source of good information:
https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project

I hope this helps.

On Tue, Oct 29, 2024 at 6:01 PM Gowrima Jayaramu <go...@gmail.com> wrote:
>
> Hi,
>
> I am a new contributor and need permissions to push the changes to Github.
> Please check the following message I received when I tried to push my
> changes,
>
> 14:57:07.225: [zookeeper] git -c credential.helper= -c core.quotepath=false
> -c log.showSignature=false push --progress --porcelain origin
> refs/heads/ZOOKEEPER-4020:refs/heads/ZOOKEEPER-4020 --set-upstream
> remote: Permission to apache/zookeeper.git denied to g-apache.
> fatal: unable to access 'https://github.com/apache/zookeeper.git/': The
> requested URL returned error: 403
> 14:57:32.508: [zookeeper] git -c credential.helper= -c core.quotepath=false
> -c log.showSignature=false push --progress --porcelain origin
> refs/heads/ZOOKEEPER-4020:refs/heads/ZOOKEEPER-4020 --set-upstream
> remote: Permission to apache/zookeeper.git denied to g-apache.
> fatal: unable to access 'https://github.com/apache/zookeeper.git/': The
> requested URL returned error: 403
>
> Thank you,
> gowrima