1
0
mirror of synced 2026-01-10 00:03:04 -05:00

Merge pull request #27854 from github/repo-sync

Repo sync
This commit is contained in:
docs-bot
2023-08-30 09:35:13 -05:00
committed by GitHub
4 changed files with 27 additions and 0 deletions

View File

@@ -15,6 +15,12 @@ shortTitle: Commit & review changes
{% data reusables.desktop.update-email-address %} For more information, see "[AUTOTITLE](/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop)."
{% ifversion repo-rules %}
Repository administrators can enable rulesets for a branch to enforce specific conventions when committing. For example, a ruleset can require a commit to be signed, or for an issue number to be referenced at the start of a commit message. {% data variables.product.prodname_desktop %} will display a warning and prevent committing if a commit does not follow the rulesets. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
{% endif %}
## Choosing a branch and making changes
1. [Create a new branch](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking {% octicon "git-branch" aria-hidden="true" %} **Current Branch** on the toolbar and selecting the branch from the list.

View File

@@ -26,6 +26,12 @@ You can always create a branch in {% data variables.product.prodname_desktop %}
{% data reusables.desktop.protected-branches %}
{% ifversion repo-rules %}
Repository administrators can also enable rulesets. Rulesets can be used to require specific branch names when creating a new branch, or to allow only users with bypass permissions to publish a new branch to the remote repository. {% data variables.product.prodname_desktop %} will show a warning and prevent the branch from being created if the branch does not follow the rulesets. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
{% endif %}
## Creating a branch
{% tip %}

View File

@@ -18,6 +18,12 @@ Before pushing changes, you should update your local branch to include any commi
{% data reusables.desktop.protected-branches %}
{% ifversion repo-rules %}
Repository administrators can also enable rulesets for a branch, which will prevent a push from completing if a ruleset has not been followed. For example, a ruleset may require a specific branch naming convention, or an issue number at the start of a commit message. {% data variables.product.prodname_desktop %} will warn about rulesets to help prevent your branch from getting into a state where you would be unable to push your changes. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
{% endif %}
## Pushing changes to {% data variables.product.prodname_dotcom %}
{% note %}

View File

@@ -17,6 +17,15 @@ topics:
shortTitle: Organization news feed
---
{% ifversion fpt or ghec %}
{% note %}
**Note:** The organization news feed is not available with {% data variables.product.prodname_emus %}.
{% endnote %}
{% endif %}
An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}.
## Accessing your organization's news feed