wip #2
Merged
wip #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What Super Linter provides: - ✅ YAML validation: Checks action.yml and workflow files syntax and formatting - ✅ Markdown linting: Validates README.md structure, links, and formatting - ✅ JSON validation: Checks test data files and any JSON configuration - ✅ Bash linting: Validates shell scripts with shellcheck - ✅ Automated formatting: Consistent style enforcement Key features: - Single action: One super-linter/super-linter@v6.8.0 action handles everything - Smart validation: Only lints changed files on PRs, full codebase on main branch pushes - Configurable: Custom linter configurations in .github/linters/ - GitHub integration: Proper permissions and status reporting Configuration files added: - .github/linters/.markdown-lint.yml: Markdown rules (120 char line length, relaxed HTML rules) - .github/linters/.yamllint.yml: YAML rules (2-space indentation, 120 char lines) This is much more maintainable than a complex custom workflow and provides professional-grade linting that scales well!
The fix changes the permissions from 600 (owner-only) to 644 (owner read/write, group/others read). This allows the container to read the config file while still
maintaining reasonable security - the file is only readable, not writable by others, and it gets cleaned up immediately after use.
The security is still maintained because:
1. The file is created with a unique name using ${{ github.run_id }}
2. It's cleaned up immediately after the container execution
3. The cleanup happens even on failure with ${{ always() }}
4. The file only exists briefly during action execution
This should resolve the permission denied error you encountered.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.