Absolutely afaik this is how all the collaborative projects work across EE4J and many other GitHub projects I’m involved in.
I also like an issue to reference in a PR and assigned to a milestone so that a feature can be discussed and release notes easy to generate although that’s not formalised anywhere, especially for
features and bug fixes.
If you need freedom to create features and push freely to branches you can do that in your GitHub fork and then when complete raise a PR either to a new GlassFish branch or to master.
I will work with Hiroki to put a wiki page together on working practices.
Steve
From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx>
On Behalf Of Gurkan Erdogdu
Sent: 17 July 2020 13:40
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Re: [glassfish-dev] Github Commit Problem
Then, is it normal not to push to the repository? Committers can only merge?
We work this way to give opportunity for review as there are many people working on the project also PRs are built and tested via Jenkins to add a level of confidence before merging.
As a committer you can merge PRs, and close issues. For master you can’t merge a PR that has zero approving reviews.
For branches you can merge PRs without review.
Committers can also close issues.
Steve
There are branch protections on master you have to raise a PR. You shouldn’t really be pushing direct to branches without going via your fork.
But, why is working this way?
Is it possible to remove this protection? I think we can move to CTR status to improve the process.
I know that the process is very slow especially on branches but if I work on the branch, I can commit every day for simple features.
There are branch protections on master you have to raise a PR. You shouldn’t really be pushing direct to branches without going via your fork.
I am trying to push the code to the GF repository. Because I am now a committer, I must able to commit and push the code but not able to do.
What are you trying to do?
My email in my GitHub Profile is the same as Eclipse account (cgurkanerdogdu@gmail) but still receive the error
Do I need to be a member of eclipse-ee4j organization in Github?
You need to ensure your GitHub credentials are associated with your Eclipse account in the profile section.
Steve
As I am now the committer for the GF project, I was trying to commit via my github credentials, but it was rejected. Is there anything I need to configure?
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
--
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
--
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
--
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
--
|