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

Instructions on using gh codespaces to run flakiness script #36

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

outofambit
Copy link
Collaborator

No description provided.

@outofambit outofambit marked this pull request as ready for review December 16, 2024 20:25
@outofambit outofambit changed the title Using gh codespaces to run flakiness script Instructions on using gh codespaces to run flakiness script Dec 16, 2024
Copy link

@ChrisC ChrisC left a comment

Choose a reason for hiding this comment

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

Overall docs are clear to me on first read! Gonna try this out tho and see if I have any more solid suggestions to make based on what I experience trying this out.

stressor/README.md Outdated Show resolved Hide resolved

## Running

1. It is prefered for you to run the stress test against your own personal "non-fork" of this repo (create a personal repo and push to it instead of using "fork" so it isn't part of the "network") to limit the number of action runs against the main branch.
1. It is prefered for you to run the stress test against your own personal "non-fork" of this repo (create a personal repo and push to it instead of using "fork" so it isn't part of the "network") to limit the number of action runs against the main branch. You generally don't want to run these tests in the copy of this repo that lives in the bocoup GitHub organization.
Copy link

Choose a reason for hiding this comment

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

@jugglinmike Given what we're learning about the generous GH Action limits on public repos, do we still want to recommend this? Keeping a personal copy of the repo as a "non-fork" is pretty hard to maintain in the long run...

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