Phabricator: Difference between revisions
No edit summary |
No edit summary |
||
Line 71: | Line 71: | ||
| | | | ||
# Stop and reconfigure apache, restart | # Stop and reconfigure apache, restart | ||
# Update phabricator config | |||
phabricator/ $ ./bin/config set phabricator.base-uri 'https://agile.bitpost.com/' | |||
# Run through the API steps again, below | # Run through the API steps again, below | ||
|} | |} | ||
Line 79: | Line 81: | ||
| The [https://thedigitalage.org/conduit/method/maniphest.query/ Phabricator API] can be used to extract a query of tasks. You need to get a (permanent) auth certificate from '''arcanist''': | | The [https://thedigitalage.org/conduit/method/maniphest.query/ Phabricator API] can be used to extract a query of tasks. You need to get a (permanent) auth certificate from '''arcanist''': | ||
m@bitpost cd development/phabricator/arcanist | m@bitpost cd development/phabricator/arcanist | ||
bin/arc set-config default https:// | bin/arc set-config default https://agile.bitpost.com/ | ||
emacs .arcconfig # and set phabricator.uri to the same | emacs .arcconfig # and set phabricator.uri to the same | ||
bin/arc install-certificate | bin/arc install-certificate | ||
That will tell you to browse [https:// | That will tell you to browse [https://agile.bitpost.com/conduit/login/ here]. | ||
You'll get an "API Token" once you log in, eg cli-5sdfksomkhgvasdlfkwfelk or whatever (NOT that one). | You'll get an "API Token" once you log in, eg cli-5sdfksomkhgvasdlfkwfelk or whatever (NOT that one). | ||
Paste API Token from that page: cli-5fxsvztkshgvtc7ssdf | Paste API Token from that page: cli-5fxsvztkshgvtc7ssdf | ||
Line 91: | Line 93: | ||
Now you can use that in the API calls to authenticate, like this: | Now you can use that in the API calls to authenticate, like this: | ||
curl https:// | curl https://agile.bitpost.com/api/maniphest.query -d api.token=cli-5fxsvztksdfsomkhgvczjtcdts | ||
Pretty easy to use once you have the initial bullshit done. It certainly isn't secure though. | Pretty easy to use once you have the initial bullshit done. It certainly isn't secure to send over the wire though. | ||
The only viable solution is to use it server-side. See bitpost.com/ci.php code for details on using good old php to get the job done. | |||
View active tokens here: | View active tokens here: | ||
https:// | https://agile.bitpost.com/settings/panel/apitokens/ | ||
|} | |} |
Revision as of 15:54, 29 April 2016
Phabricator is a solid agile project manager and issue tracker. It's customizable, here's how I use it.
WORKFLOW | CollapseDescription | |
---|---|---|
Workflow columns | Backlog => In Progress | There is a third column Fixed that can be shown, it's nice to move Resolved items there on occasion to clean up the board. |
Create a task | Click dropdown on Backlog, select Create Task. | Or you can click the large + in the top-right toolbar, select Create Task, and assign the correct Project in the tags box. |
Start a task | Drag it from Backlog to In Progress. | Drop above an existing task so the priority will be automatically set. If this is not possible, you need to manually change Priority to High so that the CI dashboard shows the task. |
Finish a task | Change Status to Resolved. | This will hide the task on the CI dashboard. It will also immediately remove the task from the board if you are only showing Open statuses. You can also drag the task from In Progress to Fixed; this has no real effect on the task, but will keep your board better organized. |
ExpandTips |
---|
ExpandMaintenance |
---|
ExpandAPI |
---|