(magpie) branch main updated: docs(dev): show where the bump workflow is started from (#1244)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/magpie.git


The following commit(s) were added to refs/heads/main by this push:
     new 123eaf77 docs(dev): show where the bump workflow is started from (#1244)
123eaf77 is described below

commit 123eaf779572c2b188f958a20bfde094b88c5fd9
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Wed Sep 16 10:41:19 2026 +0200

    docs(dev): show where the bump workflow is started from (#1244)
    
    The *Bumping the dev version* section described the Actions-tab gesture in
    prose. A capture of the page removes the guesswork about which button, since
    "Run workflow" appears twice — once to open the dropdown and once inside it to
    confirm — and both are marked.
    
    Also notes to leave *Use workflow from* on `main`: the candidate branch is cut
    from whatever ref is dispatched while the pull request is always opened against
    `main`, so dispatching from a feature branch produces a PR carrying that whole
    branch rather than just the bump.
    
    Generated-by: Claude Opus 5
---
 CONTRIBUTING.md                 |  15 +++++++++++++++
 assets/bump-dev-version-run.png | Bin 0 -> 228243 bytes
 2 files changed, 15 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 51db1ee1..3836d047 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -900,6 +900,21 @@ not something a merge can decide. `workflow_dispatch` is restricted by
 GitHub to accounts with write access, so the button is committers-only
 without the workflow checking anything itself.
 
+![The repository's Actions tab with "bump dev version" selected in the
+workflow sidebar. The run list is headed "This workflow has a
+workflow_dispatch event trigger", and a red arrow points to the **Run
+workflow** button at its right. The button's dropdown is open, showing
+"Use workflow from" with **Branch: main** selected; a second red arrow
+points to the green **Run workflow** button that confirms it. Below, a
+completed run — "bump dev version #4: Manually run by potiuk" on `main`
+— carries a green tick and a duration of 5m
+37s.](assets/bump-dev-version-run.png)
+
+Leave *Use workflow from* on `main`. The candidate branch is cut from
+whatever ref you dispatch, and the pull request is always opened against
+`main` — so dispatching from a feature branch produces a PR carrying
+that whole branch, not just the bump.
+
 One run is three jobs:
 
 ```text
diff --git a/assets/bump-dev-version-run.png b/assets/bump-dev-version-run.png
new file mode 100644
index 00000000..d07369a4
Binary files /dev/null and b/assets/bump-dev-version-run.png differ