Bot reporting "No Changeset found", but there is. How to debug?

[chizmeeple]

I've been exploring changesets recently and am in a mostly good place.

I have it working in three repos as expected.

One repo confused the bot in ways I can't understand. I keep getting:

🦋 No Changeset found

no matter what I try.

My current status:

• new branch in repo
• deleted all the files
• ran the usual:
  • yarn init
  • yarn add @changesets/cli && yarn changeset init
  • modify "commit" to true in config
  • git add .changeset/ package.json yarn.lock
  • git commit
  • git oush -u

Then I create and view the PR.

🦋 No Changeset found

This is a summary of the branch:

❯ /bin/ls -a
.                       .markdownlint.jsonc     node_modules
..                      .markdownlintignore     package.json
.changeset              .pre-commit-config.yaml terraform
.git                    .pytest_cache           yarn.lock
.infracost              .venv
❯ tree .changeset/
.changeset/
├── README.md
├── config.json
└── weak-beans-share.md

1 directory, 3 files

and

❯ cat .changeset/weak-beans-share.md
---
'botc-custom-script-json2pdf': patch
---

add changeset tool

I'm stumped, and don't know where to look for issues, not what to try to get the bot working as expected in this repo.

Any and all suggestions welcome.

[chizmeeple]

Not fully solving the issue, but possibly a pointer to the root cause, I found that removing changie files

• .changes/
• .changie.yaml

appears to confuse the bot in some way.

In a different branch where I only add the changesets tooling, and do not remove any files I see:

🦋 Changeset detected

If I run:

git rm -r .changie.yaml .changes/
git commit -m 'remove changie'
git push

the PR comment is updated to:

⚠️ No Changeset found

.changeset/ still exists after the previous operation:

❯ tree .changeset/
.changeset/
├── README.md
├── config.json
└── fair-walls-join.md

[chizmeeple]

Renaming the files does not immediately confuse the bot:

git mv .changes .no-more-changie
git commit -m 'git mv .changes .no-more-changie' --no-verify
git push

still gives the expected:

🦋 Changeset detected

However, even after renaming, removing the files confuses the bot again:

git rm -rf .no-more-changie
git commit -m 'git rm .no-more-changie' --no-verify
git push

puts us back to:

⚠️ No Changeset found

[chizmeeple]

❓ is there a limit to the number of results/files returned in octocat calls?

I have another PR in a different repo where I believe I followed the same process and the bot's fine.

The only obvious difference I can see is "Files Changed: 81" versus "Files Changed: 18"

Note: Responses include a maximum of 3000 files. The paginated response returns 30 files per page by default.

source: https://octokit.github.io/rest.js/v19#pulls-list-files