@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
Update Bug Report diviner document
Summary: Fixes T12922. For now this shuffles open source -> discouse, phacility -> phacility.
Test Plan: Regenerate diviner docs, click on new links.
Reviewers: epriestley, avivey
Reviewed By: avivey
Subscribers: avivey, Korvin
Maniphest Tasks: T12922
Differential Revision: https://secure.phabricator.com/D18229
+11
-12
+11
-12
src/docs/contributor/bug_reports.diviner
+11
-12
src/docs/contributor/bug_reports.diviner
···
12
12
13
13
For help, see @{article:Providing Reproduction Steps}.
14
14
15
+
15
16
Overview
16
17
========
17
18
···
151
152
For help, see @{article:Providing Reproduction Steps}.
152
153
153
154
154
-
Create a Task in Maniphest
155
-
==========================
155
+
For Open Source Users
156
+
=====================
156
157
157
158
If you're up to date, supported, have collected information about the problem,
158
159
and have the best reproduction instructions you can come up with, you're ready
···
161
162
It is **particularly critical** that you include reproduction steps. We will
162
163
not accept reports which describe issues we can not reproduce.
163
164
164
-
(NOTE) https://secure.phabricator.com/u/newbug/
165
+
(NOTE) https://discourse.phabricator-community.org/c/bug
165
166
166
-
If you don't want to file there (or, for example, your bug relates to being
167
-
unable to log in or unable to file an issue in Maniphest) you can file on any
168
-
other channel, but we can address reports much more effectively if they're
169
-
filed against the upstream than if they're filed somewhere else.
170
167
171
-
| Effectiveness | Filing Method |
172
-
|---|---|
173
-
| Best | Upstream Maniphest |
174
-
| Ehhh | Quora, StackOverflow, Facebook, Jelly, email, etc. |
175
-
| What | Passive-aggressive tweet |
168
+
For Phacility Customers
169
+
=======================
170
+
171
+
If you've encountered a bug via a Phacility instance or have a paid support
172
+
contract with Phacility, you can find more information on how to get help via
173
+
[[ https://admin.phacility.com/book/phacility/article/support/ | Phacility
174
+
Support ]].
176
175
177
176
178
177
Next Steps