recaptime.dev
@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
1@title Providing Version Information
2@group detail
3
4How to provide version information with reports made to the upstream.
5
6Overview
7========
8
9When you submit a bug report, we require that you include version information.
10
11Despite our insistence that users update before reporting issues, many reports
12we receive describe issues which have already been resolved. Including version
13information in your report allows us to quickly determine that you are out of
14date and that updating will fix your issue.
15
16That said, your report must also include reproduction steps, and you should be
17unable to generate valid reproduction steps for an issue which has already been
18resolved because valid reproduction steps must also reproduce against a clean,
19up-to-date install. See @{article:Providing Reproduction Steps} for details.
20
21
22Phorge Version
23==============
24
25To get Phorge version information:
26
27 - Go to the {nav Config} application. You can type "Config" into the global
28 search box, or navigate to `https://phorge.example.com/config/`. You must
29 be an administrator to access this application.
30 - Click {nav Versions} in the left menu.
31 - Copy and paste all of the information on the page into your report.
32
33
34Arcanist Version
35================
36
37To get Arcanist version information:
38
39 - Run `arc version`.
40 - Copy and paste all of the output into your report.
41
42
43Other Versions
44==============
45
46In general, we use `git` commit hashes as version identifiers, so you can
47identify the version of something by running `git show` and copy/pasting the
48hash from the output. This may be useful if you're encountering an issue which
49prevents you from reaching the version reporting screen.
50
51
52Running a Fork?
53===============
54
55If you've forked Phorge and have local commits, please make sure you are
56reporting upstream commit hashes, not local commit hashes. The UI will attempt
57to figure out where you branched from, but it may not be able to in all cases.
58
59If you report local commit hashes instead of upstream commit hashes we can not
60go look up the commit hashes to figure out which changes they correspond to, so
61we can not use that information to determine out how old your install is or
62which patches you are missing.
63
64In most cases, you can find the upstream commit you've branched from like this:
65
66```
67$ git merge-base HEAD origin/master
68```
69
70Note that if you report a bug and have local commits, we will almost always ask
71you to reproduce the issue against a clean copy of Phorge before we
72continue. You can get help faster by doing this //before// reporting an issue.
73
74
75Next Steps
76==========
77
78Continue by:
79
80 - returning to @{article:Contributing Bug Reports}.