Hey Jasmin,
As Julian mentioned, you do not need direct access to the calcite
repository on Github.
Github provides some detailed instructions on how to fork a repository
and create a pull request:
- https://docs.github.com/en/get-started/quickstart/fork-a-repo
-
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
I've also added your JIRA account to the contributors group, so you
should be able to assign issues to yourself.
Francis
On 22/10/2022 5:27 am, Julian Hyde wrote:
I don’t think you need access to the repo.
People generally create a fork of the repo, create a branch in that fork specific to the
change, and then create a pull request from that branch. For example
https://github.com/apache/calcite/pull/2937
<https://github.com/apache/calcite/pull/2937> is from Stamatis Zampetakis’
“CALCITE-5332” branch https://github.com/zabetak/calcite/tree/CALCITE-5332
<https://github.com/zabetak/calcite/tree/CALCITE-5332> to Apache main branch.
The effect of this policy is that the Apache repository does not contain very
many branches. This is a common policy in open source projects.
Also, could you please subscribe to the dev list. Your last couple of messages were
delayed (because I had to moderate them through) and you probably didn’t receive
replies. See https://calcite.apache.org/community/#mailing-lists
<https://calcite.apache.org/community/#mailing-lists>.
Julian
On Oct 21, 2022, at 9:31 AM, Jasmin Trada <[email protected]> wrote:
Hi team,
I am working on this JIRA [CALCITE-5336
<https://issues.apache.org/jira/browse/CALCITE-5336>]. I need access to the
calcite repository on GitHub to raise a pull request. Could anyone please help me
with that?
JIRA username : jtrada
GitHub username: jasmintrada
Thanks,
Jasmin
