• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

reactivando / validations-br / 17817569212
91%
master: 94%

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 18 Sep 2025 04:01AM UTC
Jobs 1
Files 37
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Sep 2025 04:01AM UTC coverage: 91.96%. Remained the same
17817569212

push

github

AZagatti
feat(ci): Adjust gh auth (#56)

* chore: remove comment

* feat(ci): Add enhanced debug workflow for push permissions

This commit adds a new test workflow (`test-push.yml`) and enhances it with extensive debugging steps to diagnose why pushes to the protected `main` branch are failing.

The workflow will now:
- Print environment variables and git configuration.
- Check npm and GitHub CLI authentication status.
- Use the GitHub CLI to inspect and print the exact branch protection rules for the `main` branch.

This will provide the necessary data to understand the root cause of the `GH006` error.

* fix(ci): Simplify and correct debug workflow for push permissions

This commit fixes the `test-push.yml` workflow. The previous version had a bug where it tried to run `gh auth login` while a `GH_TOKEN` environment variable was already set, causing a conflict.

This has been corrected by removing the unnecessary `gh auth login` and `gh auth status` steps. The workflow will now correctly use the provided `GH_PAT` to inspect branch protection rules and then attempt the test push. This should allow us to gather the necessary data to diagnose the permission issue.

* fix(ci): Update debug workflow to check auth status

This commit updates the `test-push.yml` workflow to use `gh auth status`. This is a diagnostic step to determine the identity of the user associated with the `GH_PAT` being used for authentication.

This will help us confirm our theory about why pushes to the protected `main` branch are failing. The previous attempt to inspect branch rules failed due to an incorrect field name, so this switches to a simpler and more direct `whoami`-style check.

* test(ci): Update test workflow to verify push permission fix

This commit updates the `test-push.yml` workflow to test the definitive fix for the branch protection error.

The `actions/checkout` step is now configured with a `token` input, using the `GH_PAT` secret. This should correctly authenticate al... (continued)

222 of 252 branches covered (88.1%)

Branch coverage included in aggregate %.

693 of 743 relevant lines covered (93.27%)

9.13 hits per line

Jobs
ID Job ID Ran Files Coverage
1 17817569212.1 18 Sep 2025 04:01AM UTC 37
91.96
GitHub Action Run
Source Files on build 17817569212
  • Tree
  • List 37
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #17817569212
  • 490fb7cc on github
  • Prev Build on main (#17817476209)
  • Next Build on main (#17817598274)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc