Nicola Corti
37d1e8e7a0
Act as @react-native-bot on all the actions ( #45480 )
...
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/45480
We currently use the default GITHUB_ACTION which makes a lot of interaction
appear as user "GitHub Actions". Instead we could use the `REACT_NATIVE_BOT_GITHUB_TOKEN`
which we have as secret so the bot will actually perform the actions.
Changelog:
[Internal] [Changed] - Act as react-native-bot on all the actions
Reviewed By: cipolleschi
Differential Revision: D59815201
fbshipit-source-id: 702b121ec07d0db10abf25e23f7ddf5658dd5d62
2024-07-17 03:27:12 -07:00
m-nakamura145
dd4f15bf08
chore: Bump actions/checkout ( #42952 )
...
Summary:
GitHub is [planning to upgrade to Node 20](https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/ ). Versions prior to actions/checkout v3 use an outdated version of node, so we will upgrade to actions/checkout v4, where [Node 20 is the default](https://github.com/actions/checkout/releases/tag/v4.0.0 ).
## Changelog:
<!-- Help reviewers and the release process by writing your own changelog entry.
chore: Bump actions/checkout
Pick one each for the category and type tags:
[INTERNAL] [FIXED] - chore: Bump actions/checkout
For more details, see:
https://reactnative.dev/contributing/changelogs-in-pull-requests
-->
[INTERNAL] [FIXED] - chore: Bump actions/checkout
Pull Request resolved: https://github.com/facebook/react-native/pull/42952
Reviewed By: cipolleschi
Differential Revision: D53655117
Pulled By: cortinico
fbshipit-source-id: 7c05e6ac2cb71c9d20c0b28b183cada6856f0a2d
2024-02-12 02:12:40 -08:00
kacperkapusciak
54d70cf0c6
Prevent check-for-reproducer action trigger on Umbrella and old issues ( #38664 )
...
Summary:
This PR resolves problems with too spammy `check-for-reproducer` action triggering on very old and most prominently the Umbrella issues.
Also, it brings back triggering on edited issues removed in https://github.com/facebook/react-native/pull/38634
Related to https://github.com/facebook/react-native/issues/35591
## Changelog:
[INTERNAL] [FIXED] - Prevent check-for-reproducer action trigger on Umbrella and old issues
Pull Request resolved: https://github.com/facebook/react-native/pull/38664
Test Plan: <img width="470" alt="image" src="https://github.com/facebook/react-native/assets/39658211/1d840145-1e4f-43c5-a3ea-bc16e61071ef ">
Reviewed By: cipolleschi
Differential Revision: D47868536
Pulled By: cortinico
fbshipit-source-id: fd78c38145c76f3867a41439aee5d087f38c85d2
2023-07-28 08:50:35 -07:00
Nicola Corti
ad91518fed
Let check-for-reproducer run only on newly created issues. ( #38634 )
...
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/38634
To reduce the noise of the `check-for-reproducer` bot, this restricts the event
that trigger the bot to only the issue creation.
Changelog:
[Internal] [Changed] - Let check-for-reproducer run only on newly created issues
Reviewed By: cipolleschi
Differential Revision: D47792374
fbshipit-source-id: 738a9342899e234022029e94f43b0dccebc21819
2023-07-26 03:53:59 -07:00
kacperkapusciak
3f78fa953a
Fix checkForReproducer action not adding Missing Repro comment ( #38531 )
...
Summary:
This PR fixes a bug where GitHub Actions bot didn't add a comment when "Needs: Repro" label was present in an issue.
When a maintainer adds the label manually the bot comments with "Missing Reproductible Example" as normally.
It seems like the problem occurred because of a difference in a sandbox repository and the proper facebook/react-native repo environment.
My sandbox that I used to test https://github.com/facebook/react-native/pull/38338 had an "bot" account with Personal Access Token setup to reply to issues. Turns out that bots using PAT have more permissions and can trigger one action from the other.
**The solution is to send the comment directly from the `checkForReproducer` action.** This won't collide with other actions but sadly will duplicate the sending logic into two actions.
This PR also makes the bot respect when a maintainer removes and adds a label by hand and won't alter the maintainer decision.
Related to ☂️ https://github.com/facebook/react-native/issues/35591
## Changelog:
[INTERNAL] [FIXED] - Message
Pull Request resolved: https://github.com/facebook/react-native/pull/38531
Test Plan: 
Reviewed By: cipolleschi
Differential Revision: D47666922
Pulled By: cortinico
fbshipit-source-id: 4a6a471cb11c6ed9b48263d18bf8e283577a14bb
2023-07-21 08:46:03 -07:00
kacperkapusciak
5705661d1f
Fix issue bot triggering on PRs ( #38525 )
...
Summary:
This PR fixes a bug with an issue labeling bot issues triggering on comments to pull requests. The action doesn't trigger when a pull request is open (but other actions add comments immediately).
From [GitHub docs](https://docs.github.com/en/webhooks-and-events/events/issue-event-types ):
> GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. [...] Pull requests have a **`pull_request` property in the `issue` object.**
☝️ Which is a way to differentiate between an issue and a pull request
Relates to a bug introduced in https://github.com/facebook/react-native/pull/38338 and links to ☂️ https://github.com/facebook/react-native/issues/35591
## Changelog:
[INTERNAL] [FIXED] - Prevent issue bot triggering on pull requests
Pull Request resolved: https://github.com/facebook/react-native/pull/38525
Test Plan:
This PR makes use of `github.event.issue.pull_request` object which is null on issues and comments in issues:

and truthy on comments on pull requests

With a change from PR bot skips execution on comments on pull requests

Reviewed By: ryancat
Differential Revision: D47628330
Pulled By: cortinico
fbshipit-source-id: 63e7180bb57ffd34904414a702c02019e18a042b
2023-07-21 03:10:12 -07:00
kacperkapusciak
42a2898617
Add check-for-reproducer action ( #38338 )
...
Summary:
This PR adds a "check-for-reproducer" GitHub action proposed in https://github.com/facebook/react-native/issues/35591 .
This GitHub action automatically labels an issue with when no link to GitHub repository under the authors name or link to Snack is present either in the issue body or in the comments.
## Changelog:
<!-- Help reviewers and the release process by writing your own changelog entry.
Pick one each for the category and type tags:
[ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message
For more details, see:
https://reactnative.dev/contributing/changelogs-in-pull-requests
-->
[INTERNAL] [ADDED] - Add check-for-reproducer GitHub action
Pull Request resolved: https://github.com/facebook/react-native/pull/38338
Test Plan:
This action was tested on a private repro mimicking on how GitHub actions are set-up in `facebook/react-native` repository. If you'd want to play around with the action on this private repo just ask for access - provided you're a maintainer.
### Regarding issue body
1. Labels "Needs: Repro" when no link to Expo Snack or a Github repo under the author's name is present in the issue body:

2. Removes the "Needs: Repro" label and deletes the Missing Repro comment when the author edits the issue and provides a link to GitHub repo under their name

3. Removes the "Needs: Repro" label and deletes the Missing Repro comment when the author edits the issue and provides a valid link to Expo Snack

### Regarding comments
3. Removes the "Needs: Repro" label and deletes the Missing Repro comment when there's a comment with a link to reproduction under issue author's name

4. Removes the "Needs: Repro" label and deletes the Missing Repro comment when there's a comment with a link to Expo Snack

### Regarding false-positives
5. Adds a "Needs: Repro" label when a link to reprository isn't under the issue author's name

6. Adds a "Needs: Repro" label when a link to Expo Snack's homepage was sent

7. Adds a "Needs: Repro" label when a random link was sent

Reviewed By: NickGerleman
Differential Revision: D47511745
Pulled By: cortinico
fbshipit-source-id: 2c0e5a989f52b4e50992a3954283f122b14153e0
2023-07-19 02:38:28 -07:00