~sircmpwn/sr.ht-dev

sr.ht-docs: Mention the one-manifest-per-basename behaviour v1 PROPOSED

наб: 1
 Mention the one-manifest-per-basename behaviour

 1 files changed, 4 insertions(+), 0 deletions(-)
Export patchset (mbox)
How do I use this?

Copy & paste the following snippet into your terminal to import this patchset into git:

curl -s https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/13888/mbox | git am -3
Learn more about email & git
View this thread in the archives

[PATCH sr.ht-docs] Mention the one-manifest-per-basename behaviour Export this patch

---
 git.sr.ht/index.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/git.sr.ht/index.md b/git.sr.ht/index.md
index 017cc57..f5336ba 100644
--- a/git.sr.ht/index.md
+++ b/git.sr.ht/index.md
@@ -82,6 +82,10 @@ following command:
git config --add push.pushOption submit=".sourcehut/*.yml"
```

Only one manifest per basename is supported, e.g. if you submit both
`.builds/alpine.yml` and `.deploy/alpine.yml`, an undetermined one
will be submitted under the `alpine.yml` name.

## Changing the default branch

If you wish to change your default branch, visit the settings tab of your
-- 
2.20.1
I wonder if it'd be better if we printed a warning on push which
clarified which one it submitted and which one(s) were skipped.