omp/rsi
1
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Remove the .pm board; requirements now live in Gitea issues #12

Open
omp wants to merge 1 commits from chore/remove-pm-board into main
pull from: chore/remove-pm-board
merge into: omp:main
Conversation 1 Commits 1 Files Changed 4 +5 -74
omp commented 2026-10-05 07:39:38 -07:00
Owner
Copy Link

The pm-board web UI and its task runner are retired in goodcode/pm-board#38. Every requirement on this project's board was already migrated to a Gitea issue labelled Requirement, and every implementation choice to an issue labelled Choice, so this file has no remaining source.

Deleted: .pm/board.yaml, .pm/gitea-url

References that pointed into .pm/ were rewritten to the Gitea issues that replaced them.

The workflow for this project is now: requirements are Gitea issues, feedback lives on Gitea threads, and agent work runs in an isolated worktree under a tmux session.

The pm-board web UI and its task runner are retired in goodcode/pm-board#38. Every requirement on this project's board was already migrated to a Gitea issue labelled `Requirement`, and every implementation choice to an issue labelled `Choice`, so this file has no remaining source. Deleted: `.pm/board.yaml`, `.pm/gitea-url` References that pointed into `.pm/` were rewritten to the Gitea issues that replaced them. The workflow for this project is now: requirements are Gitea issues, feedback lives on Gitea threads, and agent work runs in an isolated worktree under a tmux session.
complexity-12.png
75 KiB
complexity-12.png
omp added 1 commit 2026-10-05 07:39:39 -07:00 
The pm-board web UI and its task runner are retired in goodcode/pm-board#38.
Every requirement on this board was migrated to a Gitea issue labelled
`Requirement` and every implementation choice to an issue labelled `Choice`,
so the local board file has no remaining source.
omp commented 2026-10-10 11:54:30 -07:00
Author
Owner
Copy Link

Code complexity — PR #12

complexity by pull request

The complexity of this pull request could not be measured (its revision is not available locally); the chart shows the pull requests that could.

Chart: no pull request revision was available to measure.
Not measured (revision or diff unavailable locally): #1, #2, #3, #12.

<!-- complexity sha=b451e4932b6bf143355f54cd3fbc1d1c87ec4c75 --> ## Code complexity — PR #12 ![complexity by pull request](https://git.jajahome.duckdns.org/attachments/da8e6d0f-d926-4ec4-b66e-b416285b5217) The complexity of this pull request could not be measured (its revision is not available locally); the chart shows the pull requests that could. Chart: no pull request revision was available to measure. Not measured (revision or diff unavailable locally): #1, #2, #3, #12.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin chore/remove-pm-board:chore/remove-pm-board
git checkout chore/remove-pm-board
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Choice
Requirement
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
omp
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: omp/rsi#12
No description provided.
Delete Branch "chore/remove-pm-board"

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?