@yachiyo-5i/xlyra-agent 0.2.0 → 1.0.2
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 +23 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -284,6 +284,29 @@ ANTHROPIC_MODEL=<model>
|
|
|
284
284
|
|
|
285
285
|
Smoke tests make real model requests and may incur provider charges.
|
|
286
286
|
|
|
287
|
+
A PR body should cover at least:
|
|
288
|
+
|
|
289
|
+
- Background and problem: why the change is needed
|
|
290
|
+
- Goals and non-goals: what this PR does and does not address
|
|
291
|
+
- Approach and implementation: key design decisions and trade-offs
|
|
292
|
+
- Change details: concrete changes by module
|
|
293
|
+
- Compatibility and impact: APIs, configuration, protocols, data, dependencies, performance, and user behavior
|
|
294
|
+
- Tests and verification: commands, coverage, failure paths, and manual checks
|
|
295
|
+
- Documentation and migration: required updates or upgrade steps
|
|
296
|
+
- Risks, rollback, and follow-up work
|
|
297
|
+
- Security checks and reviewer notes
|
|
298
|
+
|
|
299
|
+
The repository PR template guides authors through these sections. A PR containing only a change summary and test result is incomplete; write `none` or `not applicable` when a section does not apply.
|
|
300
|
+
|
|
301
|
+
Recommended branch protection for `main`:
|
|
302
|
+
|
|
303
|
+
- Require a Pull Request before merging
|
|
304
|
+
- Require the CI status check
|
|
305
|
+
- Require the `Pull Request title` check
|
|
306
|
+
- Require at least one approving review
|
|
307
|
+
- Dismiss stale approvals after new commits
|
|
308
|
+
- Block force pushes and direct pushes
|
|
309
|
+
|
|
287
310
|
## Publishing with GitHub Actions
|
|
288
311
|
|
|
289
312
|
The repository includes CI verification, Release Please, and a GitHub Release-triggered npm publishing workflow. Publishing uses npm Trusted Publishing with GitHub OIDC, so no long-lived npm token is stored in GitHub.
|