@fromeroc9/testform 1.0.7 → 1.0.9
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 +2 -2
- package/dist/action/index.js +11 -29
- package/dist/cli/index.js +5 -23
- package/package.json +1 -2
package/README.md
CHANGED
|
@@ -30,9 +30,9 @@ We highly recommend using our automated **[Install Testform Labels and Project](
|
|
|
30
30
|
- Configure the "Status" field with the correct options and colors (`Todo`, `Done`, `passed`, `failed`, `blocked`, `skipped`, `unexecuted`).
|
|
31
31
|
- Install the `close-issue.yml` workflow into your target repository to automate issue state transitions.
|
|
32
32
|
|
|
33
|
-
> **💡 Authentication Recommendation:** If you plan to use Testform within GitHub Actions, or authenticate via `
|
|
33
|
+
> **💡 Authentication Recommendation:** If you plan to use Testform within GitHub Actions, or authenticate via `testform login` (or equivalent CLI login), we strongly advise configuring a **Personal Access Token (PAT)** (with `repo` and `project` permissions). *Note: It is neither mandatory nor recommended to use a GitHub App token.*
|
|
34
34
|
>
|
|
35
|
-
> *Why?* The default `GITHUB_TOKEN` provided by Actions often lacks the necessary scopes to manipulate organization-level GitHub Projects (V2) or perform cross-repository operations. Using a dedicated PAT
|
|
35
|
+
> *Why?* The default `GITHUB_TOKEN` provided by Actions often lacks the necessary scopes to manipulate organization-level GitHub Projects (V2) or perform cross-repository operations. Using a dedicated PAT ensures that your automated pipelines have the robust, fine-grained access required to smoothly transition issues, manage test cases, and keep your project boards flawlessly in sync.
|
|
36
36
|
|
|
37
37
|
## Installation
|
|
38
38
|
|