Skip to content

Handle member errors in launch - #214

Open
geoand wants to merge 2 commits into
mainfrom
handle-failures
Open

Handle member errors in launch#214
geoand wants to merge 2 commits into
mainfrom
handle-failures

Conversation

@geoand

@geoand geoand commented Apr 16, 2026

Copy link
Copy Markdown
Contributor

With this change, a single member failure
does not cause the entire loop to fail.
Instead, a new issue is created that contains
all the failed members

N.B. We'll need to create the ci-failure label

@geoand

geoand commented Apr 16, 2026

Copy link
Copy Markdown
Contributor Author

@geoand geoand changed the title Handle member errors Handle member errors in launch Apr 16, 2026
Comment thread .github/workflows/ecosystem-action.yml Outdated

@gastaldi gastaldi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@gastaldi

gastaldi commented Apr 17, 2026

Copy link
Copy Markdown
Member

I wonder if we should close the #216 issue manually if it's open and the build passes?

@geoand

geoand commented Apr 17, 2026

Copy link
Copy Markdown
Contributor Author

Yeah, that definitely makes sense. Let me try and update the PR

With this change, a single member failure
does not cause the entire loop to fail.
Instead, a new issue is created that contains
all the failed members
Comment thread .github/workflows/ecosystem-action.yml Outdated
with:
github-token: ${{ secrets.ECOSYSTEM_CI_TOKEN }}
script: |
const issueNumber = 216;

@gastaldi gastaldi Jun 3, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

For maintainability purposes, it would be better if we had that in an env var (since it's also declared in the workflow step below)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants