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

mbland / elistman / 6150360194 / 1
100%
main: 100%

Build:
DEFAULT BRANCH: main
Ran 11 Sep 2023 06:33PM UTC
Files 38
Run time 2s
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

11 Sep 2023 06:26PM UTC coverage: 100.0%. Remained the same
6150360194.1

push

github

mbland
Set GitHub Actions OIDC provider permissions

Attempting to fix the CI/CD breakage via "unset-current-credentials:
true" in commit aed7091a4 didn't work:

- https://github.com/mbland/elistman/actions/runs/6150150355/job/16687535254

Digging deeper, I realized that the token.actions.githubusercontent.com
OIDC provider in my IAM providers was created yesterday when I ran "sam
pipeline bootstrap" for mbland/ses-forwarder. A search for GitHub
Actions OIDC provider documentation turned up:

- https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers#adding-permissions-settings

Comparing the .github/workflows/pipeline.yaml for ses-forwarder created
yesterday to the elistman version showed that the new file contained the
"permissions:" block in this change.

2253 of 2253 relevant lines covered (100.0%)

15.97 hits per line

Source Files on job 6150360194.1
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 6150360194
  • 025fbcd1 on github
  • Prev Job for on main (#6150150355.1)
  • Next Job for on main (#6150392606.1)
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