You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documenting the changes I made yesterday and today.
Prologue
Throughout this issue, I used square brackets [] to represent the change's scope wherever possible.
Changes
I have enabled the option to use the PRs title as the default commit message for the merge commit as suggested by @sebastiaanspeck in the chatroom earlier today. [All repos]
I have enabled the delete the head branch by default when the PR is merged [A few repos in which it wasn't enabled] (Note: The branch is still easily recoverable even after deletion)
I have enabled the option to suggest updating the PRs branch when there are changes in the default branch(This is to avoid issues in the main repo where contributors build on top of their existing branch and oftentimes existing pages/commits by different people are displayed as new additions/modifications. [All repos]
I disabled merge using a merge commit option in tlrc as we follow the same across our repos and suggest Squash & merge or Rebase & merge PRs as the default workflow.
I enabled Private Vulnerability reporting, Dependabot version updates and Secret Scanning Alerts in Security Settings for tlrc as we follow it throughout the Org.
Reference Images (post the changes)
Edit.
Additionally, I have enabled the Push protection (on the Org) when a supported secret is detected i.e. deploy keys, etc. Although it is highly unlikely that someone might commit a secret, IG it's better to be cautious.
The text was updated successfully, but these errors were encountered:
kbdharun
changed the title
[Archive] Repo settings changes and standardization throughout the Organization
[Archive] Repositories settings changes and standardization throughout the Organization
Oct 23, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
archiveArchive of changes made in tldr-pages, etc.
Documenting the changes I made yesterday and today.
Prologue
Throughout this issue, I used square brackets
[]
to represent the change's scope wherever possible.Changes
tlrc
as we follow the same across our repos and suggest Squash & merge or Rebase & merge PRs as the default workflow.tlrc
as we follow it throughout the Org.Reference Images (post the changes)
Edit.
Additionally, I have enabled the Push protection (on the Org) when a supported secret is detected i.e. deploy keys, etc. Although it is highly unlikely that someone might commit a secret, IG it's better to be cautious.
The text was updated successfully, but these errors were encountered: