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

Move gitea URL config into board.yaml #2

Open
omp wants to merge 1 commits from chore/config-in-board-yaml into main
pull from: chore/config-in-board-yaml
merge into: omp:main
Conversation 2 Commits 1 Files Changed 2 +1 -1
omp commented 2026-09-22 01:40:59 -07:00
Owner
Copy Link

The gitea_url top-level key in .pm/board.yaml replaces the .pm/gitea-url marker file (one line added to the config file, marker deleted; no board items touched).

Why: pm-board's follow-up review on goodcode/pm-board PR #2 (goodcode/pm-board#2) moved all configuration into the config file .pm/board.yaml, keeping state and config separate, with no backwards compatibility. pm-board and its task runner now read this option from the gitea_url key only.

Merge this before or together with the pm-board change and pull the local checkout, so the deployed project page keeps its Gitea link.

The `gitea_url` top-level key in `.pm/board.yaml` replaces the `.pm/gitea-url` marker file (one line added to the config file, marker deleted; no board items touched). Why: pm-board's follow-up review on goodcode/pm-board PR #2 (https://git.jajahome.duckdns.org/goodcode/pm-board/pulls/2) moved all configuration into the config file `.pm/board.yaml`, keeping state and config separate, with no backwards compatibility. pm-board and its task runner now read this option from the `gitea_url` key only. Merge this before or together with the pm-board change and pull the local checkout, so the deployed project page keeps its Gitea link.
complexity-2.png
75 KiB
complexity-2.png
omp added 1 commit 2026-09-22 01:41:00 -07:00 
The gitea_url top-level key in .pm/board.yaml replaces the .pm/gitea-url
marker file; pm-board and its task runner read config only from the
config file now (no backwards compatibility).
omp commented 2026-09-26 10:33:05 -07:00
Author
Owner
Copy Link

Superseded by #3, which does this migration (marker file to gitea_url board key) plus the pm-board R17 runtime cleanup (delete .pm/gitea-url, ignore runner files). Recommend closing this one in favor of #3.

Superseded by #3, which does this migration (marker file to `gitea_url` board key) plus the pm-board R17 runtime cleanup (delete `.pm/gitea-url`, ignore runner files). Recommend closing this one in favor of #3.
omp commented 2026-10-10 11:54:26 -07:00
Author
Owner
Copy Link

Code complexity — PR #2

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=59c869fba1db2f69c1d2b7c7e74d4e31b7481f1a --> ## Code complexity — PR #2 ![complexity by pull request](https://git.jajahome.duckdns.org/attachments/38ec9707-22cc-4a6f-b5a5-3df6fd4a7fbf) 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/config-in-board-yaml:chore/config-in-board-yaml
git checkout chore/config-in-board-yaml
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#2
No description provided.
Delete Branch "chore/config-in-board-yaml"

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?