1st PR trigger vs 1st PR merged difference

[polarathene]

I don't know if this affects the store per se. But iirc, @gatsbybot would only add a message to a PR when the author's 1st PR opened was merged, if a PR since then had been added and merged, @gatsbybot did not trigger on that PR instead.

It's a minor issue, although did have me confused as I had started contributing in late December and had a couple PRs accepted before my first one was merged 2 or so months after it was initially opened, which is when I got the invitation for swag at the store(I hadn't checked prior).

[jlengstorf]

@polarathene can you say more about this? It should trigger when your first PR is merged, regardless of other PRs being open.

If that didn’t happen, can you please send links to your PRs so we can dig into this a bit? Thanks!

[polarathene]

Here are my PRs(filtered by closed which they all are presently).

My first PR submitted to Gatsby is this one,
and this is my first merged PR.

I would have expected the bot to congratulate me on the first PR that was actually merged, not wait until my first submitted PR was merged(which I imagine for some when rejected, they'd never hear from the bot?).

Swag store worked fine though, it had recognized the merged PR prior to the bot congratulating my first submitted PR on being merged.

---

So just to clarify:

• Swag store logic works fine once a PR is merged.
• The bot congratulates once the first submitted PR is merged, not on the first merged PR.

[jlengstorf]

@gatsbyjs/core @gatsbyjs/ecosystem something is weird here, and I'm not quite sure how this is possible, but apparently Peril is following the first PR, not the first merged PR. 😕

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contributefor more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜