forge
/
build.sh
3
2
Fork 1
Code Issues 6 Pull Requests Releases Wiki Activity

Support ordering of tasks #6

New Issue
Open
opened 2020-04-19 13:23:16 +00:00 by southerntofu · 1 comment
southerntofu commented 2020-04-19 13:23:16 +00:00
Owner
Copy Link

run-parts style ordering for tasks would be nice in some situations.

Iterating over tasks should produce them in the right order. We should just find an elegant way to strip the digits (eg. 10-buildblog -> buildblog) in task name, but keep it for file-based operations

run-parts style ordering for tasks would be nice in some situations. Iterating over tasks should produce them in the right order. We should just find an elegant way to strip the digits (eg. 10-buildblog -> buildblog) in task name, but keep it for file-based operations
southerntofu commented 2020-04-25 16:35:34 +00:00
Author
Owner
Copy Link

Proposal: maybe strip the "NN-" prefix by default, but provide the full name as $GITBUILDFILE environment variable for tasks who would want to keep it.

Proposal: maybe strip the "NN-" prefix by default, but provide the full name as `$GITBUILDFILE` environment variable for tasks who would want to keep it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: forge/build.sh#6
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?