Thanks Naba - I'll try to adapt :)
On 10/31/19 7:33 PM, Nabarun Nag wrote:
It is how Github branch protection is designed.
This is my explanation from the information provided by you :
- The Pull Request you mentioned had 11 commits and when you tried to
merged it, I assume you tried to squash
It is how Github branch protection is designed.
This is my explanation from the information provided by you :
- The Pull Request you mentioned had 11 commits and when you tried to
merged it, I assume you tried to squash it to a single commit. It generates
a new SHA.
- When you are pushing that SH
I just want to know why my PR that passed the tests and was approved
couldn't be pushed from the command line Naba
On 10/31/19 5:11 PM, Nabarun Nag wrote:
Hi Bruce,
This was what was discussed in multiple email chains last week. GitHub
branch protection was enabled on the develop branch.
Comm
I just want to know why my PR that passed the tests and was approved
couldn't be pushed from the command line Nab
On 10/31/19 5:11 PM, Nabarun Nag wrote:
Hi Bruce,
This was what was discussed in multiple email chains last week. GitHub
branch protection was enabled on the develop branch.
Comma
Hi Bruce,
This was what was discussed in multiple email chains last week. GitHub
branch protection was enabled on the develop branch.
Command-line and the merge button on the website have the same effect. This
has now being implemented in a lot of Apache projects and we are
implementing it as the
Was there a pull request for this SHA?
On Thu, Oct 31, 2019, 16:36 Bruce Schuchardt wrote:
> I just completed GEODE-7358 and was prevented from pushing from the
> command-line. The Merge button on github worked, but why can't I have
> command-line control of the process? I don't like giving co
I just completed GEODE-7358 and was prevented from pushing from the
command-line. The Merge button on github worked, but why can't I have
command-line control of the process? I don't like giving control of my
merge to a web-site button. We should revert this change!
geode> git push --no-ve
