@veda-hq/niyam 0.7.6 → 0.7.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +22 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -646,7 +646,8 @@ names the slice and was made after the slice was last added, and for a
|
|
|
646
646
|
dropped State when it names the State and was made after the State was
|
|
647
647
|
closed. They read the Approvals issue's comments once a check, only when a
|
|
648
648
|
decision is owed. If GitHub cannot find the Approvals issue, it answers
|
|
649
|
-
nothing and the check goes on.
|
|
649
|
+
nothing and the check goes on. The shared Guard takes the same answer, if it
|
|
650
|
+
is unedited, for a slice added after the approval (#501; see Guard).
|
|
650
651
|
|
|
651
652
|
A `Decision:` comment, a batch answer included, counts only while it says
|
|
652
653
|
what owners wrote: unedited, or edited by owners alone. Repo writers, agents included, can edit anyone's
|
|
@@ -1727,7 +1728,7 @@ tag and the commit. Install the attached package on each machine with pnpm,
|
|
|
1727
1728
|
once; nothing is built on install:
|
|
1728
1729
|
|
|
1729
1730
|
```bash
|
|
1730
|
-
pnpm add -g https://github.com/veda-hq/niyam/releases/download/v0.7.
|
|
1731
|
+
pnpm add -g https://github.com/veda-hq/niyam/releases/download/v0.7.8/veda-hq-niyam-0.7.8.tgz
|
|
1731
1732
|
```
|
|
1732
1733
|
|
|
1733
1734
|
The package puts one command on `PATH`, `niyam`. Since P-57 a release
|
|
@@ -1829,6 +1830,25 @@ item (for a slice added later, when the owner's `Decision:` settled it):
|
|
|
1829
1830
|
**Guards:** `.github/workflows/ci.yml`, `scripts/*.mjs`, `.githooks/`
|
|
1830
1831
|
```
|
|
1831
1832
|
|
|
1833
|
+
For a slice added later, the first unedited answer from an owner since the
|
|
1834
|
+
slice joined counts, wherever it is:
|
|
1835
|
+
- a `Decision:` on the slice;
|
|
1836
|
+
- a `Decision:` on its Work item naming it;
|
|
1837
|
+
- a batch answer on the Approvals issue the default branch's settings name
|
|
1838
|
+
(`"approvals": N`), whose first line opens `Decision: approve` and names the
|
|
1839
|
+
slice, as the work rules read it (#501).
|
|
1840
|
+
|
|
1841
|
+
If GitHub cannot find the Approvals issue, Guard counts nothing from it and
|
|
1842
|
+
goes on. Any other failure to read it fails closed.
|
|
1843
|
+
|
|
1844
|
+
**Mergify's merge queue (#507).** Mergify tests a queued pull request in a draft of its own:
|
|
1845
|
+
- opened as `mergify[bot]` on a `mergify/merge-queue/` branch of the repository;
|
|
1846
|
+
- titled `merge queue: checking #A on main (sha)`, with `, stacked on #B` when it tests several.
|
|
1847
|
+
|
|
1848
|
+
Guard judges that draft's own diff once with each tested pull request's title, author and body. It refuses a file only when every tested pull request leads to that refusal. So a guard file passes when one tested pull request's approved slice names it, or when its onboard or Dependabot exemption holds for the draft's diff. Guard never passes a draft solely because it is Mergify's: a file still needs a tested pull request's owner-approved slice, unless an existing onboard or Dependabot exemption applies.
|
|
1849
|
+
|
|
1850
|
+
Any other draft, or one whose title names no pull request, is judged as itself, and so is any draft where work rules are off. A tested pull request GitHub cannot give fails closed.
|
|
1851
|
+
|
|
1832
1852
|
A name is a path, a folder ending in `/`, or a pattern where `*` matches
|
|
1833
1853
|
within one folder and `**` across them. The guard files are a floor every
|
|
1834
1854
|
repository has, everything under `.github/`, `.githooks/` and `.husky/`,
|