Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): Identify which repository flaky tests were reported for #2

Merged
merged 3 commits into from
Oct 23, 2024

Conversation

matheus23
Copy link
Contributor

@matheus23 matheus23 commented Oct 23, 2024

Description

Should show the repo name in discord messages when flaky tests are reported.

See the generated discord message here: https://discord.com/channels/949724860232392765/1194275793220665375/1298551980314071093

Also fixes the documentation preview comment (and I've enabled the github page for it): https://n0-computer.github.io/iroh-blobs/pr/2/docs/iroh_blobs/

Change checklist

  • Self-review.
  • [ ] Documentation updates following the style guide, if relevant.
  • [ ] Tests if relevant.
  • [ ] All breaking changes documented.

@matheus23 matheus23 self-assigned this Oct 23, 2024
Copy link

github-actions bot commented Oct 23, 2024

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh-blobs/pr/2/docs/iroh_blobs/

Last updated: 2024-10-23T08:19:19Z

This aligns this PR with the main iroh repo PR.
Copy link
Contributor

@Arqu Arqu left a comment

Choose a reason for hiding this comment

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

I technically had this whole part removed from the repo, but @rklaehn force pushed main so that got lost. Maybe we can keep it now.

@matheus23 matheus23 merged commit a666957 into main Oct 23, 2024
25 checks passed
@matheus23 matheus23 deleted the matheus23/identify-flaky-repo branch October 23, 2024 08:26
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.

2 participants