You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -59,14 +59,20 @@ Then you should be good to go.
59
59
60
60
We force the use of [`pull_request_target`](https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/) as a workflow event to ensure that someone cannot change the CODEOWNER files at the same time as having that change be used to validate if they can merge.
61
61
62
-
### Issue / PR closing
62
+
### Issue / PR manipulation
63
63
64
64
Merging a PR has strict security requirements, but closing a PR or Issue can have a weaker one. Anyone with a GitHub login in the CODEOWNER has the ability to close any PR / Issue via a comment/review which includes:
65
65
66
66
```
67
67
@github-actions close
68
68
```
69
69
70
+
A closed PR can be re-opened with:
71
+
72
+
```
73
+
@github-actions reopen
74
+
```
75
+
70
76
### Extras
71
77
72
78
You can use this label to set labels for specific sections of the codebase, by having square brackets to indicate labels to make: `[label]`
0 commit comments