Skip to content

Add the community files this repository was missing - #4

Merged
ftymoshchuk merged 1 commit into
mainfrom
claude/eloquent-ptolemy-dsy07a
Sep 29, 2026
Merged

ftymoshchuk merged 1 commit into
mainfrom
claude/eloquent-ptolemy-dsy07a

Conversation

@ftymoshchuk

Copy link
Copy Markdown
Member

docs/new-repository.md lists community files for every public repository, and this one had none of its own. So GitHub showed the org-wide defaults from sigrix-io/.github: a CONTRIBUTING.md about the marketplace, and a security policy sending reports to support@sigrix.io, unlike every other public repository.

Changes

  • SECURITY.md: reports go to security@sigrix.io, like the other public repositories. It describes what the two actions actually hold, checked against both action.yml files:

    • They run inside the calling job with its permissions and take no secret as an input.
    • Checkout uses the job's GITHUB_TOKEN, as actions/checkout does at its defaults.
    • The install input reaches the shell through env: with globbing off.
    • Every upstream action is pinned to a commit.

    In scope: caller input executed as code, fetching anything besides the pinned actions and the named package, and verify-published-package passing a release the index doesn't serve.

  • CONTRIBUTING.md: what fits, drawn from README.md ("What belongs here, and what does not"; why these are composite actions rather than reusable workflows); CI as the test run; and the pull request rules the actions already follow (commit pins with version comments, input through env:, a changelog line consumers read before bumping).

  • CODE_OF_CONDUCT.md: byte-identical to the other repositories' copy.

  • Blank issues off, a defect form and a change form. The defect form asks for the calling step and warns that a run log can carry tokens or private names. The change form asks which repositories would use the change, since something only one repository wants belongs in that repository.

  • .github/pull_request_template.md: asks whether a caller sees the change and which CI step covers it.

  • A CHANGELOG.md line. Documentation only; neither action changes.

Checked locally

  • Each form and config.yml passed a structural check against GitHub's issue-form schema. The same check passes sigrix-mcp's and sigrix-runtime's existing forms.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso


Generated by Claude Code

docs/new-repository.md lists them for every public repository, and this
one had none of its own, so GitHub showed the organisation-wide defaults:
a CONTRIBUTING.md about the marketplace, and a SECURITY.md sending
reports to a different address from every other repository's.

- SECURITY.md: reports to security@sigrix.io, like the other public
  repositories, and what these actions actually hold. They run inside
  the calling job with its permissions and take no secret as an input;
  checkout uses the job's GITHUB_TOKEN at actions/checkout's defaults;
  the install input reaches the shell through env with globbing off.
- CONTRIBUTING.md: what fits, drawn from the README (a mechanism every
  Sigrix package wants; a package's claims about itself stay in the
  caller), CI as the test run, and the pull request rules the actions
  already follow: commit pins with version comments, input through env,
  a changelog line consumers read before bumping.
- CODE_OF_CONDUCT.md, byte-identical to the other repositories'.
- Blank issues off, a defect form and a change form, and a pull request
  template asking whether a caller sees the change.

Documentation only; neither action changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso
@ftymoshchuk
ftymoshchuk merged commit ef47d29 into main Sep 29, 2026
7 checks passed
@ftymoshchuk
ftymoshchuk deleted the claude/eloquent-ptolemy-dsy07a branch September 29, 2026 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants