chore 📦: Comment out --exclude-files option in pr-check.yaml workflow Add new rule to ignore placeholder secrets in README.md #22

Closed
Jose wants to merge 0 commits from dev into main
Owner

Updated the PR check workflow to comment out the --exclude-files option and added a new rule in README.md to ignore placeholder secrets.

Updated the PR check workflow to comment out the `--exclude-files` option and added a new rule in README.md to ignore placeholder secrets.
Jose added 16 commits 2026-02-14 10:29:56 +01:00
feat : Add PR check workflow for Gitleaks and lint tests
Some checks failed
ansible-lint / Ansible Lint (push) Failing after 6s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
aad77acf42
This commit introduces a new pull request (PR) check workflow that includes Gitleaks for security scanning and lint tests to ensure code quality.
refactor ♻️: Refactor PR check workflow by consolidating steps and removing redundant code
Some checks failed
ansible-lint / Ansible Lint (push) Failing after 6s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 7s
945717ffbb
This refactoring consolidates the steps in the PR check workflow, reducing redundancy and improving efficiency.
fix 🐛: Fix typo in PR check workflow comments
Some checks failed
ansible-lint / Ansible Lint (push) Failing after 6s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 5s
1733801fe5
Corrected a minor spelling error in the comments of the pull request check workflow to improve readability and clarity.
fix 🐛: Fix typo in PR check comment body
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 11s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 19s
PR check / Gitleaks (pull_request) Failing after 5s
PR check / lint tests (pull_request) Successful in 14s
PR check / handle_failures (pull_request) Has been skipped
PR check / handle_success (pull_request) Has been skipped
a0138b1bea
Corrected a minor spelling error in the comment body of the pull request check to improve readability and accuracy.
refactor ♻️: Refactor condition for handle_failures to run regardless of previous job results
Some checks failed
ansible-lint / Ansible Lint (push) Failing after 6s
Gitleaks Scan / gitleaks (push) Successful in 6s
ai-reviews / Review PR (pull_request) Successful in 19s
Markdown Lint / markdown-lint (push) Successful in 5s
PR check / Gitleaks (pull_request) Failing after 5s
PR check / lint tests (pull_request) Failing after 9s
PR check / handle_failures (pull_request) Successful in 2s
PR check / handle_success (pull_request) Has been skipped
dfda760d2c
This refactoring ensures that the `handle_failures` function is executed irrespective of the outcomes of previous jobs, improving the robustness and reliability of the system.
docs 📝: Update README title and compatibility matrix format
Some checks failed
ansible-lint / Ansible Lint (push) Failing after 6s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 6s
eb5eaf7887
Updated the README title to be more descriptive and restructured the compatibility matrix for better readability.
fix 🐛: Fix PR check job condition
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 11s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 21s
PR check / Gitleaks (pull_request) Failing after 6s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 1s
PR check / handle_success (pull_request) Has been skipped
fc3b5e8507
This commit addresses an issue where the PR check job was not running as expected. The condition for triggering the job has been corrected to ensure it runs properly under all circumstances.
docs 📝: Update README.md section title and minor formatting
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 10s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 28s
PR check / Gitleaks (pull_request) Failing after 4s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 1s
PR check / handle_success (pull_request) Has been skipped
e21f9bd002
Corrected the title of a section in the README.md file and made some minor formatting adjustments for better readability.
chore 📦: Update Gitleaks configuration and README
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 12s
Gitleaks Scan / gitleaks (push) Failing after 5s
Markdown Lint / markdown-lint (push) Successful in 5s
c9a6f0e092
Add `--config-path .gitleaks.toml` to pr-check.yaml and create a new `.gitleaks.toml` file with allowlist and rules for security scanning. Rename 'API utilities' to 'Utilities' in the README.md table.
docs 📝: Comment out allowlist rule for badge URLs in README
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 12s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 30s
PR check / Gitleaks (pull_request) Failing after 4s
PR check / lint tests (pull_request) Successful in 15s
PR check / handle_failures (pull_request) Successful in 2s
PR check / handle_success (pull_request) Has been skipped
dbd70e61ce
Updated the README to comment out the allowlist rule for badge URLs, as it is no longer necessary.
refactor ♻️: Refactor Gitleaks command option from --config-path to --config
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 12s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 35s
PR check / Gitleaks (pull_request) Failing after 5s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 2s
PR check / handle_success (pull_request) Has been skipped
7b5c802689
Updated the configuration path option for Gitleaks from '--config-path' to '--config' to simplify usage and improve consistency with other tools.
chore 📦: Update redaction setting in PR check workflow
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 12s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 35s
PR check / Gitleaks (pull_request) Failing after 4s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 2s
PR check / handle_success (pull_request) Has been skipped
eb5bde86d6
This commit updates the redaction setting from `--redact=10` to `--redact=false` in the `.gitea/workflows/pr-check.yaml` file. This change ensures that no redaction occurs during the PR check process, maintaining full visibility and integrity of the data being checked.
fix 🐛: Increase redaction level in PR check workflow
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 11s
Gitleaks Scan / gitleaks (push) Successful in 4s
ai-reviews / Review PR (pull_request) Successful in 24s
Markdown Lint / markdown-lint (push) Successful in 5s
PR check / Gitleaks (pull_request) Failing after 4s
PR check / lint tests (pull_request) Successful in 16s
PR check / handle_failures (pull_request) Successful in 2s
PR check / handle_success (pull_request) Has been skipped
76f035768c
This change updates the redaction level from `false` to `100` in the `.gitea/workflows/pr-check.yaml` file. This ensures that more sensitive information is redacted during pull request checks, enhancing security.
chore 📦: Reduce redaction level in Gitleaks check
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 12s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 30s
PR check / Gitleaks (pull_request) Failing after 4s
PR check / lint tests (pull_request) Successful in 14s
PR check / handle_failures (pull_request) Successful in 2s
PR check / handle_success (pull_request) Has been skipped
276c438ff4
Lowered the redaction level in the Gitleaks configuration to improve log readability while maintaining security.
chore 📦: Increase redaction length and exclude README.md in gitleaks check
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 12s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 26s
PR check / Gitleaks (pull_request) Failing after 4s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 1s
PR check / handle_success (pull_request) Has been skipped
2d9aa39339
This commit increases the maximum redaction length for sensitive data in our codebase and updates the gitleaks configuration to exclude README.md files from scans. This ensures that we maintain a higher standard of security while avoiding false positives.
chore 📦: Comment out --exclude-files option in pr-check.yaml workflow Add new rule to ignore placeholder secrets in README.md
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 11s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 4s
ai-reviews / Review PR (pull_request) Successful in 19s
PR check / Gitleaks (pull_request) Failing after 5s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 1s
PR check / handle_success (pull_request) Has been skipped
8bd90b8823
Updated the PR check workflow to comment out the `--exclude-files` option and added a new rule in README.md to ignore placeholder secrets.
gitea-actions bot reviewed 2026-02-14 10:30:34 +01:00
gitea-actions bot left a comment

Review Summary

  • .gitea/workflows/pr-check-yaml: This appears to be a GitHub Actions workflow for checking PRs, including leak tests, linting, and labeling. The provided diff indicates that the entire file has been deleted. This is problematic as it removes all checks and automation in place for reviewing PRs. To maintain proper code quality, ensure that these checks are not removed without careful consideration and a suitable replacement or alternative is implemented.
  • .gitea/workflows/pr-check.yaml: Summary: Addition of a new GitHub Actions workflow file for CI checks. The provided code looks good, and no issues with Score >= 2 were found.
  • .gitleaks.toml: Summary: This Git diff describes the addition of a Gitleaks configuration file to help filter out sensitive data from the codebase, and it also includes some custom rules for API keys and Sidekiq secrets. Overall, the changes look good and should improve the security of the project. However, there is one issue related to the entropy value that might require attention:
  • README.md: Summary: The provided code change updates the README file to better align with Ansible conventions and clarifies some terms. No significant issues were found concerning logic, security, performance, or maintainability. LGTM
# Review Summary * **.gitea/workflows/pr-check-yaml**: This appears to be a GitHub Actions workflow for checking PRs, including leak tests, linting, and labeling. The provided diff indicates that the entire file has been deleted. This is problematic as it removes all checks and automation in place for reviewing PRs. To maintain proper code quality, ensure that these checks are not removed without careful consideration and a suitable replacement or alternative is implemented. * **.gitea/workflows/pr-check.yaml**: **Summary:** Addition of a new GitHub Actions workflow file for CI checks. The provided code looks good, and no issues with Score >= 2 were found. * **.gitleaks.toml**: **Summary:** This Git diff describes the addition of a Gitleaks configuration file to help filter out sensitive data from the codebase, and it also includes some custom rules for API keys and Sidekiq secrets. Overall, the changes look good and should improve the security of the project. However, there is one issue related to the entropy value that might require attention: * **README.md**: **Summary:** The provided code change updates the README file to better align with Ansible conventions and clarifies some terms. No significant issues were found concerning logic, security, performance, or maintainability. ``` LGTM ```

[Score: 2] The entropy value for the "generic-api-key-docs" rule seems too high. This could potentially mask sensitive information in the README.md file. Consider lowering it if necessary.

[Score: 2] The entropy value for the "generic-api-key-docs" rule seems too high. This could potentially mask sensitive information in the README.md file. Consider lowering it if necessary.

CI checks failed.

Leak: failure
Lint: success

<!--ci-failed-comment--> ❌ CI checks failed. Leak: failure Lint: success
gitea-actions bot closed this pull request 2026-02-14 10:30:57 +01:00
Some checks failed
ansible-lint / Ansible Lint (push) Successful in 11s
Gitleaks Scan / gitleaks (push) Successful in 4s
Markdown Lint / markdown-lint (push) Successful in 4s
ai-reviews / Review PR (pull_request) Successful in 19s
PR check / Gitleaks (pull_request) Failing after 5s
PR check / lint tests (pull_request) Successful in 13s
PR check / handle_failures (pull_request) Successful in 1s
PR check / handle_success (pull_request) Has been skipped

Pull request closed

Sign in to join this conversation.