@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
fork

Configure Feed

Select the types of activity you want to include in your feed.

Remove scattered links to "Support" document

Summary:
I'm going to do some version of D13941. Clean up extra links to the old document first.

These were just randomly links from various places that we no longer really want feedback on and/or are now better covered by other documents.

Test Plan:
- `grep`
- Reviewed Config/Welcome screen.
- Reviewed `uri.allowed-editor-protocols`.

Reviewers: chad

Reviewed By: chad

Differential Revision: https://secure.phabricator.com/D14303

+10 -41
+2 -12
src/applications/config/controller/PhabricatorConfigWelcomeController.php
··· 225 225 'fa-globe', 226 226 $content); 227 227 228 - $support_href = PhabricatorEnv::getDoclink('Give Feedback! Get Support!'); 229 - $content = pht( 230 - "=== Need Help with Setup? ===\n\n". 231 - 'Having trouble getting something set up? See '. 232 - '**[[ %s | Give Feedback! Get Support! ]]** for ways to get in touch '. 233 - 'to get answers to questions, report bugs, and request features.', 234 - $support_href); 235 - 236 - $explore[] = $this->newItem( 237 - $request, 238 - 'fa-life-ring', 239 - $content); 228 + // TODO: Restore some sort of "Support" link here, but just nuke it for 229 + // now as we figure stuff out. 240 230 241 231 $differential_uri = PhabricatorEnv::getURI('/differential/'); 242 232 $differential_create_uri = PhabricatorEnv::getURI(
+2 -7
src/applications/config/option/PhabricatorSecurityConfigOptions.php
··· 20 20 } 21 21 22 22 public function getOptions() { 23 - $support_href = PhabricatorEnv::getDoclink('Give Feedback! Get Support!'); 24 - 25 23 $doc_href = PhabricatorEnv::getDoclink('Configuring a File Domain'); 26 24 $doc_name = pht('Configuration Guide: Configuring a File Domain'); 27 25 ··· 197 195 ->setSummary(pht('Whitelists editor protocols for "Open in Editor".')) 198 196 ->setDescription( 199 197 pht( 200 - "Users can configure a URI pattern to open files in a text ". 201 - "editor. The URI must use a protocol on this whitelist.\n\n". 202 - "(If you use an editor which defines a protocol not on this ". 203 - "list, [[ %s | let us know ]] and we'll update the defaults.)", 204 - $support_href)) 198 + 'Users can configure a URI pattern to open files in a text '. 199 + 'editor. The URI must use a protocol on this whitelist.')) 205 200 ->setLocked(true), 206 201 $this->newOption( 207 202 'celerity.resource-hash',
-5
src/docs/user/userguide/arcanist.diviner
··· 129 129 - Another common approach is to write an install script as an action into 130 130 existing build scripts, so users can run `make install-arc` or 131 131 `ant install-arc` or similar. 132 - - In general, if this sucks and is causing you pain, let us know (see 133 - @{article:Give Feedback! Get Support!}). We're planning to improve this at 134 - some point, but it's somewhat complicated to get right. While it can take a 135 - little time to set up, we aren't getting feedback that it's a persistent 136 - pain point, so it hasn't been a priority. 137 132 138 133 == Installing Tab Completion == 139 134
+1 -5
src/docs/user/userguide/audit.diviner
··· 12 12 This document summarizes the post-push "audit" workflow implemented by the 13 13 creatively-named //Audit// tool. 14 14 15 - NOTE: The audit workflow is new, give us feedback about it! See 16 - @{article:Give Feedback! Get Support!}. 17 - 18 15 = How Audit Works = 19 16 20 17 Using auditing allows you to push and deploy code without waiting for code ··· 104 101 105 102 = Next Steps = 106 103 107 - - Learn more about Herald at @{article:Herald User Guide}; or 108 - - give us feedback at @{article:Give Feedback! Get Support!}. 104 + - Learn more about Herald at @{article:Herald User Guide}.
+1 -2
src/docs/user/userguide/differential.diviner
··· 65 65 - learn about handling large changesets at 66 66 @{article:Differential User Guide: Large Changes}; or 67 67 - learn about test plans at @{article:Differential User Guide: Test Plans}; or 68 - - learn more about Herald at @{article:Herald User Guide}; or 69 - - give us feedback at @{article:Give Feedback! Get Support!}. 68 + - learn more about Herald at @{article:Herald User Guide}.
+2 -6
src/docs/user/userguide/phame.diviner
··· 5 5 6 6 = Overview = 7 7 8 + IMPORTANT: Phame is a prototype application. 9 + 8 10 Phame is a simple blogging platform. You can write drafts which only you can 9 11 see. Later, you can publish these drafts as posts which anyone who can access 10 12 the Phabricator instance can see. You can also add posts to blogs to increase ··· 55 57 A given comment widget is tied 1:1 with a given post. This means the same 56 58 instance of a given comment widget will appear for a given post regardless 57 59 of whether that post is being viewed in the context of a blog. 58 - 59 - = Next Steps = 60 - 61 - - Phame is extremely new and very basic for now. Give us feedback on 62 - what you'd like to see improve! See @{article:Give Feedback! Get 63 - Support!}.
+2 -4
src/docs/user/userguide/phriction.diviner
··· 3 3 4 4 Construct a detailed written history of your civilization. 5 5 6 - = Overview = 6 + Overview 7 + ======== 7 8 8 9 Phriction is a simple wiki. You can edit pages, and the text you write will stay 9 10 there. Other people can see it later. 10 - 11 - NOTE: Phriction is extremely new and very basic for now. Give us feedback on 12 - what you'd like to see improve! See @{article:Give Feedback! Get Support!}.