Closed larshp closed 3 years ago
The feature is there. The squash/rebase culture not yet.
by updating the repo settings, everything will be squashed. Squashing might not be optimal in all cases, but its good to have as the single allowed merge strategy
also, keep branches up to date before merging, something like below,
yeah, let's setup some rules to have a clean commit history, that invites devs to look at. Admin @schneidermic0 can you configure the repo as suggested above?
I have changed the settings as suggested above
Branch protection missing? Should see something like
I have just seen it...
Branch protection has been setup as well, now. Maybe, I have to slightly change it for the JSON validation, tomorrow. I have also added that a review is required by at least one person.
cool, looks good to me, closing, we can update the settings if something needs updating
Suggest setting the merge button to be squash(under repo settings)
this will give fewer commits in the main branch, one commit per PR merge