Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Improve Linux/container portability documentation #69

New Issue
Open
opened 2026-07-02 05:43:31 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:43:31 -05:00
Owner
Copy Link
Copy Source

Current documentation and scripts heavily assume macOS workflows, including keychain and provenance handling. Add Linux/container guidance for running the MCP server and scripts.

Acceptance criteria

  • README or docs explain Linux setup.
  • Documents environment-variable-based credential loading.
  • Documents how to run tests on Linux.
  • Documents how to run the MCP server in a container or headless environment if supported.
  • Clarifies which scripts are macOS-specific.
  • scripts/clear-provenance is documented as macOS-specific.
  • No secrets are added to docs.
Current documentation and scripts heavily assume macOS workflows, including keychain and provenance handling. Add Linux/container guidance for running the MCP server and scripts. ## Acceptance criteria * README or docs explain Linux setup. * Documents environment-variable-based credential loading. * Documents how to run tests on Linux. * Documents how to run the MCP server in a container or headless environment if supported. * Clarifies which scripts are macOS-specific. * `scripts/clear-provenance` is documented as macOS-specific. * No secrets are added to docs.
jcwalker3 added the documentationportability labels 2026-07-02 05:44:03 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label documentation portability
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#69
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?