Something went wrong. Try again.
@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.) hq.recaptime.dev/wiki/Phorge
phorge phabricator
Something went wrong. Try again.
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182@title Diffusion User Guide: Permanent Refs@group userguideExplains when Diffusion will take actions in response to discovering commits.Overview========Diffusion can close tasks and revisions and take other actions when commitsappear in a repository (either because they were pushed to Phorge, orbecause they were pushed to some remote which Phorge is observing).This document explains when Diffusion acts on commits and how to configure thisbehavior.Publishing Commits==================Diffusion distinguishes between "pushed" and "published" commits.Not all commits that are pushed to a repository are destined for greatness:for example, many tools push temporary commits to secret places like`refs/pull/123`, `refs/notes/*`, or `refs/changes/12/345678/1`.Sometimes, human users intentionally push changes to branches like"tmp-hack-ignore-123". This is formally discouraged by Phorge, but thepractice is so widespread that we've given up trying to stop anyone from doingit.Phorge will import these commits and create pages for them so you can viewthem in the web UI and link to them, but does not take any other actions untilthey are "published".A commit is "published" when it becomes reachable from a permanent ref. Bydefault, all branches are permanent refs, so pushing a commit to "master" willpublish it, but pushing a commit to `refs/pull/123` (either directly, or byusing a tool like GitHub) will not.Usually, commits are published by pushing them directly to a permanent branchlike "master", or by merging a temporary branch into a permanent branch.When a commit is published, Phorge acts on it and: - sends email; - delivers notifications; - publishes a feed story; - triggers Audits; - runs Herald rules; - updates mentioned objects; - closes referenced tasks; and - closes associated revisions.Configuring Repositories========================You can control publishing behavior in two primary ways: by configuringwhich refs are considered to be permanent refs, and by disabling publishingentirely.By default, all branches are considered permanent refs and all other refs(including tags and other arbitrary custom refs) are considered nonpermanent.This means that, by default, pushing commits to a branch like"tmp-hack-ignore-123" will publish those commits.If you want to be free to push commits to temporary branches like this andonly want commits on certain branches (like "master") to be published,configure which refs are treated as permanent by editing{nav Branches > Permanent Refs} from the "Manage" page of the repository.To disable publishing entirely, select {nav Basics > Disable Publishing}.Next Steps==========Continue by: - troubleshooting in greater depth with @{article:Troubleshooting Repository Imports}.