Last year, Jan started a thread with different topics and one of them was
to have a merge convention. I copy the text:
> 3. Merge Conventions / Protected Branch:
> Connected to all that is my suggestion to protect the `master` branch so
that by default nobody can commit there - all changes have t
I would agree that "squash + merge" should be used in *most* cases,
and I think there is no dispute on this point.
In the few cases where there are too many things for a "squash +
merge" commit, and we have the changes down to a limited number of
clean, sensible commits, then I would favor merging
+1 to protect the master branch.
Forcing PR will help organize commits if we need to go back in
time to determine the reason why a change was made as the
commit in github will show the corresponding PR. Which will
(hopefully) be properly filled out with context and motivation,
as well as the issu
-1 for protected master branches, we are a small group of committers and
don't need rules to keep us honest.
Protecting master would involve infra, as we cannot manage the minutia in
github. I think we all do this anyway except for rare occasions.
+1 for squash and merge, as long as the meaningfu
Hi, folks,
(Note: You're receiving this email because you're on the dev@ list for
one or more Apache Software Foundation projects.)
For ApacheCon North America 2019, we asked projects to participate in
the creation of project/topic specific tracks. This was very successful,
with about 15 projects
Nightly build #1189 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1189/consoleFull
-
Jenkins for Apache Cordova
---
