Skip to content

docs: improve README with comprehensive secrets usage guide - #6033

Closed
vincent067 wants to merge 1 commit into
nektos:masterfrom
vincent067:docs/improve-secrets-documentation
Closed

docs: improve README with comprehensive secrets usage guide#6033
vincent067 wants to merge 1 commit into
nektos:masterfrom
vincent067:docs/improve-secrets-documentation

Conversation

@vincent067

Copy link
Copy Markdown

Summary

This PR adds comprehensive documentation for using secrets with act, addressing the confusion reported in #2651.

Changes

Added a new "Using Secrets with act" section to README.md covering:

Documentation Added

  1. Method 1: Command Line (Interactive) - How to pass secrets via -s flag with both inline values and secure prompts
  2. Method 2: Secret File - Using .secrets files with --secret-file flag
  3. Method 3: Environment Variables - Leveraging existing env vars

Security Best Practices

  • Warning about never committing secrets
  • Reminder to add .secrets to .gitignore (already present)
  • Recommendation to use interactive prompts when possible
  • Suggestion for .secrets.example pattern

Practical Example

A complete workflow example showing how to use secrets in a deployment scenario, with the corresponding act command.

Why This Helps

New users often struggle with understanding how to pass secrets to their local workflow runs. This documentation:

  • Provides clear, actionable instructions
  • Emphasizes security best practices
  • Includes practical examples
  • Covers all three methods supported by act

Testing

  • Verified markdown formatting
  • Checked all code examples
  • Confirmed .secrets is already in .gitignore

Thanks for maintaining this awesome tool!

Closes #2651

@ChristopherHX

Copy link
Copy Markdown
Contributor

The readme is no longer the docs of nektos/act, please visit our nektosact.com and press suggest an edit to make changes.

@ChristopherHX ChristopherHX left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add comprehensive documentation for using secrets with act including:
- Command line secrets usage with -s flag
- Secrets file configuration (.secrets)
- Automatic GITHUB_TOKEN handling
- Practical workflow examples
- Security best practices

Closes nektos#2651
@vincent067
vincent067 force-pushed the docs/improve-secrets-documentation branch from 5f6afd9 to f9bddb7 Compare March 24, 2026 18:59
@panekj

panekj commented Mar 28, 2026

Copy link
Copy Markdown
Contributor

This is just re-stating what user guide already says and also I'm pretty sure it's LLM slop.

@panekj panekj closed this Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants