Tools and tasks contributors to develop their own extensions
Details
Details
Description
Yesterday
Yesterday
aklapper updated the task description for T15982: Update the documentation for "Adding New CSS and JS" to not exclude extensions.
Sat, Feb 1
Sat, Feb 1
Arkus404 added 1 auditor(s) for rP42234d56e5a4: Remove unused PhabricatorApplicationTransactionCommentView::getStatusID(): Arkus404.
Fri, Jan 31
Fri, Jan 31
amybones added a comment to T15982: Update the documentation for "Adding New CSS and JS" to not exclude extensions.
A comment in two parts:
First and most relevant to this task: It certainly would be nice to get some of this into documentation! It took me quite awhile to figure this out when doing my own extension development.
Jan 14 2025
Jan 14 2025
Cigaryno moved T15030: Support a Phorge Extensions ecosystem from Backlog to Meta on the Phactory: Community Projects board.
Cigaryno moved T15568: Make extension installation more seamless from Backlog to Meta on the Phactory: Community Projects board.
Dec 26 2024
Dec 26 2024
Dec 25 2024
Dec 25 2024
valerio.bozzolan added a comment to T15519: arc-unit on phorge should ignore any currently installed extensions.
How an extension can have their unit tests then? 🤔
Cigaryno moved T15519: arc-unit on phorge should ignore any currently installed extensions from Backlog to Dev Tools on the Extension Development board.
Cigaryno moved T15557: Don't require extensions to `load` phorge/arcanist for linters from Backlog to Dev Tools on the Extension Development board.
Cigaryno moved T15030: Support a Phorge Extensions ecosystem from Backlog to Phactory on the Extension Development board.
Cigaryno moved T15568: Make extension installation more seamless from Backlog to Phactory on the Extension Development board.
Cigaryno moved T15718: Guide/demo on "How To Create Your First Extension" from Backlog to Phactory on the Extension Development board.
Cigaryno moved T15730: Tool to manage Extensions Installation (Phorge) from Backlog to Phactory on the Extension Development board.
Dec 24 2024
Dec 24 2024
Cigaryno moved T15568: Make extension installation more seamless from Backlog to Phactory on the Phorge board.
Cigaryno moved T15730: Tool to manage Extensions Installation (Phorge) from Backlog to Phactory on the Phorge board.
Cigaryno moved T15030: Support a Phorge Extensions ecosystem from Backlog to Phactory on the Phorge board.
Jun 16 2024
Jun 16 2024
mturdus closed Q139: Add remarkup syntax help for custom remarkup rule tokens as resolved.
avivey updated the question details for Q139: Add remarkup syntax help for custom remarkup rule tokens.
Jun 13 2024
Jun 13 2024
Apr 6 2024
Apr 6 2024
tsc edited the content of How to Write Extensions.
Apr 5 2024
Apr 5 2024
avivey placed T15030: Support a Phorge Extensions ecosystem up for grabs.
Did that Phactory: Hosting Projects Here
Mar 20 2024
Mar 20 2024
@avivey to do now:
Feb 17 2024
Feb 17 2024
avivey edited the content of How to Write Extensions.
avivey created an object: How to Install Extensions.
Feb 16 2024
Feb 16 2024
avivey created an object: How to Write Extensions.
Feb 6 2024
Feb 6 2024
Lectrician1 added a comment to T15011: Build a Phorge Developer Environment.
I've used phorge-devcontainer as well and it works great!
speck added a comment to T15011: Build a Phorge Developer Environment.
I managed to compile xhpast on windows using llvm installed via Scoop. I also have Visual Studio C++ 19 installed which may be required (I saw some suspicious output that indicated that some include files were being pulled from that install somehow).
Feb 3 2024
Feb 3 2024
Jan 24 2024
Jan 24 2024
Jan 22 2024
Jan 22 2024
valerio.bozzolan added a comment to T15718: Guide/demo on "How To Create Your First Extension".
Nice. Maybe a start-extension Arcanist workflow is a bit overkill, but a boilerplate extension would be lovely