Page MenuHomePhabricator
Differential D20434 Diff 48788 src/docs/user/userguide/diffusion_managing.diviner

Changeset View

Standalone View

View Options

src/docs/user/userguide/diffusion_managing.diviner

Show First 20 Lines • Show All 131 Lines • ▼ Show 20 Lines
This option is only available in Git and Mercurial, because it is impossible This option is only available in Git and Mercurial, because it is impossible
to make dangerous changes in Subversion. to make dangerous changes in Subversion.
This option has no effect if a repository is not hosted because Phabricator This option has no effect if a repository is not hosted because Phabricator
can not prevent dangerous changes in a remote repository it is merely can not prevent dangerous changes in a remote repository it is merely
observing. observing.
Basics: Disable Publishing
==========================
You can disable publishing for a repository. For more details on what this
means, see @{article:Diffusion User Guide: Permanent Refs}.
This is primarily useful if you need to perform major maintenance on a
repository (like rewriting a large part of the repository history) and you
don't want the maintenance to generate a large volume of email and
notifications. You can disable publishing, apply major changes, wait for the
new changes to import, and then reactivate publishing.
Basics: Deactivate Repository Basics: Deactivate Repository
============================= =============================
Repositories can be deactivated. Deactivating a repository has these effects: Repositories can be deactivated. Deactivating a repository has these effects:
- the repository will no longer be updated; - the repository will no longer be updated;
- users will no longer be able to clone/fetch/checkout the repository; - users will no longer be able to clone/fetch/checkout the repository;
- users will no longer be able to push to the repository; and - users will no longer be able to push to the repository; and
▲ Show 20 Lines • Show All 134 Lines • ▼ Show 20 Lines
======== ========
The **Branches** panel allows you to configure how Phabricator interacts with The **Branches** panel allows you to configure how Phabricator interacts with
branches. branches.
This panel is not available for Subversion repositories, because Subversion This panel is not available for Subversion repositories, because Subversion
does not have formal branches. does not have formal branches.
You can configure **Default Branch**. This controls which branch is shown by You can configure a **Default Branch**. This controls which branch is shown by
default in the UI. If no branch is provided, Phabricator will use `master` in default in the UI. If no branch is provided, Phabricator will use `master` in
Git and `default` in Mercurial. Git and `default` in Mercurial.
If you want Diffusion to ignore some branches in the repository, you can **Fetch Refs**: In Git, if you are observing a remote repository, you can
configure **Track Only**. Other branches will be ignored. If you do not specify specify that you only want to fetch a subset of refs using "Fetch Refs".
any branches, all branches are tracked.
Normally, all refs (`refs/*`) are fetched. This means all branches, all tags,
and all other refs.
If you want to fetch only a few specific branches, you can list only those
branches. For example, this will fetch only the branch "master":
```
refs/heads/master
```
You can fetch all branches and tags (but ignore other refs) like this:
```
refs/heads/*
refs/tags/*
```
This may be useful if the remote is on a service like GitHub, GitLab, or
Gerrit and uses custom refs (like `refs/pull/` or `refs/changes/`) to store
metadata that you don't want to bring into Phabricator.
**Permanent Refs**: To learn more about permanent refs, see:
- @{article:Diffusion User Guide: Permanent Refs}
By default, Phabricator considers all branches to be permanent refs. If you
only want some branches to be treated as permanent refs, specify them here.
When specifying branches, you should enter one branch name per line. You can When specifying branches, you should enter one branch name per line. You can
use regular expressions to match branches by wrapping an expression in use regular expressions to match branches by wrapping an expression in
`regexp(...)`. For example: `regexp(...)`. For example:
| Example | Effect | | Example | Effect |
|---------|--------| |---------|--------|
| `master` | Track only `master`. | `master` | Only the `master` branch is a permanent ref.
| `regexp(/^release-/)` | Track all branches which start with `release-`. | `regexp(/^release-/)` | Branches are permanent if they start with `release-`.
| `regexp(/^(?!temp-)/)` | Do not track branches which start with `temp-`. | `regexp(/^(?!temp-)/)` | Branches named `temp-` are not permanent.
Actions
======
The **Actions** panel can configure notifications and publishing behavior.
Normally, Phabricator publishes notifications when it discovers new commits.
You can disable publishing for a repository by turning off **Publish/Notify**.
This will disable notifications, feed, and Herald (including audits and build
plans) for this repository.
When Phabricator discovers a new commit, it can automatically close associated
revisions and tasks. If you don't want Phabricator to close objects when it
discovers new commits, disable **Autoclose** for the repository.
Staging Area Staging Area
============ ============
The **Staging Area** panel configures staging areas, used to make proposed The **Staging Area** panel configures staging areas, used to make proposed
changes available to build and continuous integration systems. changes available to build and continuous integration systems.
▲ Show 20 Lines • Show All 98 Lines • Show Last 20 Lines
Phabricator · Built by Phacility