Skip to content

Fix stale README references for CI and testing#4650

Closed
Bojun-Vvibe wants to merge 1 commit intofacebook:devfrom
Bojun-Vvibe:agent/facebook_zstd-1776704753
Closed

Fix stale README references for CI and testing#4650
Bojun-Vvibe wants to merge 1 commit intofacebook:devfrom
Bojun-Vvibe:agent/facebook_zstd-1776704753

Conversation

@Bojun-Vvibe
Copy link
Copy Markdown

Repo: facebook/zstd (⭐ 25000)
Type: docs
Files changed: 1
Lines: +5/-3

What

Updates the top-level README to point readers at the current CI workflow location and the actual local test script path. The change replaces a dead reference to .travis.yml with .github/workflows/, and fixes the testing instructions from playTest.sh in src/tests to tests/playTests.sh from the repository root.

Why

The existing README sends contributors to a file that no longer exists and documents a test command that cannot work as written. Fixing both keeps the first-run contributor experience accurate, avoids avoidable confusion during local validation, and aligns the README with the current repository layout.

Testing

Verified the referenced paths locally in the repository:

  • .github/workflows/ exists and contains the active CI workflow files.
  • tests/playTests.sh exists.
    No runtime checks were needed because this is a documentation-only change.

Risk

Low - documentation-only update that aligns README instructions with files already present in the repo.

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented Apr 20, 2026

Hi @Bojun-Vvibe!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@Bojun-Vvibe Bojun-Vvibe closed this by deleting the head repository Apr 21, 2026
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