Repository navigation
docs: README for authors: before, submit, what happens next, how long - #15
Open
thesprockee wants to merge 2 commits into
Open
thesprockee wants to merge 2 commits into
thesprockee wants to merge 2 commits into
Conversation
Plain-words walk through the author side: what to have ready, the form and its check, the maintainer review, the EchoTools copy that is built and signed, how a version is released, how long it takes, what the author gets back and what players see. Says plainly that the copy and signing are rolling out mod by mod and that releases from the author's repo work as before until then. Closes #12 Co-Authored-By: Andrew Bates <a@sprock.io>
The template's release workflow opens a draft, and the submission check sees only published releases. Say so, and say that this release is the author's and unsigned, and that the signed one is what the EchoTools copy's draft becomes after review. Refs #12 Co-Authored-By: Andrew Bates <a@sprock.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR 3 of 3 of Spritz's order (after #8 and #14). Closes #12.
What
README.mdrewritten for authors, in plain words, from the signing design's author-facing section: before you submit, submitting, what happens next (approval gives an EchoTools copy; PR to the copy, maintainer review, tag, draft, signing, publish, launcher picks it up), how long it takes, what you get back, what players see, testing your own builds. Pull-a-version and the label table are kept.Where it says less than the design
AGENTS.mdlink at the end points at the file added by ci: AGENTS.md and the pull-request gates #14, so it resolves once ci: AGENTS.md and the pull-request gates #14 is merged.Added after Spritz's review note
Step 4 of "Before you submit" now says to publish the template's draft release in your own repo before submitting (the check reads published releases only), that this release is the author's and unsigned, and that the signed release is what the EchoTools copy's draft becomes after review.
Commands run
Docs only: no code, no failing-first test applies.
Co-Authored-By: Andrew Bates a@sprock.io