Commit Graph

39 Commits

Author SHA1 Message Date
Peter Evans
5fc4efd1a4 docs: update readme 2025-10-01 16:20:14 +01:00
Peter Evans
0355148dbf docs: update readme
Just some minor changes to keep things consistent with the style of my other actions repos
2025-07-09 08:58:08 +01:00
Roger Oba
d33623bdcd docs: make it clear what's required for a same-repo dispatch. (#411) 2025-07-07 08:13:34 +01:00
Peter Evans
ff45666b94 feat: update runtime to node 20 (#305) 2024-01-25 20:57:43 +09:00
Peter Evans
0fd5c8a50c Add multiline client payload example 2023-09-29 20:08:49 +09:00
Peter Evans
da2ccb0fc8 docs: add link to fine-grained pat 2023-07-05 10:12:12 +09:00
Bruno Juchli
4d042f3cdd docs: document fine grained access token (#227) 2023-07-05 10:09:29 +09:00
Dan Roscigno
87c5425cae Update README.md (#153)
Added the repository to the example usage for a remote repo.
2023-01-26 09:34:40 +09:00
Peter Evans
b155cf1427 Update readme 2022-12-08 12:05:57 +09:00
Peter Evans
faa2bf022d Update readme 2022-12-08 11:46:02 +09:00
Peter Evans
cb18cc8cd6 Update readme 2022-10-21 17:51:56 +09:00
Peter Evans
1f873ff42d Remove token elevation 2022-10-21 15:56:27 +09:00
Peter Evans
2f6d32ce83 Update docs 2022-10-19 16:34:26 +09:00
Peter Evans
66463e47e7 Update docs 2022-10-19 16:28:06 +09:00
Vinícius Vargas
3c4e552d10 Update README.md 2022-10-10 05:38:56 -03:00
Vinícius Vargas
77fb463884 Fix: Information related to tokens in README
Fix documentation related to tokens. The secrets.GITHUB_TOKEN provided by the GitHub Actions App can do everything related to the repo if we elevate its permissions, including calling workflow_dispatch and repository_dispatch.

Some people in my organization are using PAT's instead of the secrets.GITHUB_TOKEN when using this action because of this README suggestion, even when they are calling the same repository. Using PATs in that contexts provides unnecessary security risks.
2022-10-10 05:37:25 -03:00
Peter Evans
64c665535e Update readme 2022-03-22 13:10:44 +09:00
Peter Evans
8d9724ed37 Update runtime to node 16 2022-03-22 12:54:49 +09:00
Peter Evans
f7b4de6b26 Update default branch 2021-05-12 17:29:28 +09:00
Markus Staab
111788c696 Update README.md 2020-09-24 11:05:07 +09:00
Markus Staab
f131b1d1f9 Update README.md 2020-09-24 11:05:07 +09:00
Markus Staab
1b0d3fa47b Update README.md 2020-09-19 07:59:30 +02:00
Markus Staab
6de120f0ca Update README.md 2020-09-19 07:58:31 +02:00
Markus Staab
1f8e017ab8 Mention string length limitations 2020-09-19 07:56:36 +02:00
Peter Evans
c0fe68ba01 Update readme 2020-08-04 15:54:46 +09:00
Peter Evans
f540f114fd Update readme 2020-06-25 09:13:39 +09:00
Cristiano Betta
8e9f439e9f Clarify that PAT owner needs to have repo access
Ran into an issue where I was using a user that did not have explicit access to the repo that I was trying to trigger an event for. I'm not sure if the user needs write access to the repo, but it seems logical to me that someone with `read` only access can not trigger GH actions.
2020-06-24 14:57:02 +01:00
Peter Evans
7ecf080487 Update README 2020-05-29 10:21:14 +09:00
Peter Evans
c830a9705e Update README 2020-05-25 18:16:20 +09:00
Peter Evans
a4bb1fc8bc Add ci badge 2020-05-05 14:11:28 +09:00
Peter Evans
3d4567b16c Update README 2020-05-04 18:20:48 +09:00
Peter Evans
22b027c6f6 Update README 2020-04-13 10:05:30 +09:00
Peter Evans
1e4d1b6ee6 Update README 2020-03-06 11:34:24 +09:00
Peter Evans
c8b367eb2d Update to checkout v2 2020-01-04 09:36:01 +09:00
Peter Evans
23c9cd4b68 Update README 2019-12-05 01:18:06 +09:00
Peter Evans
ee6a038929 Update README 2019-11-13 23:26:52 +09:00
Peter Evans
aaad5096a7 Update README 2019-11-11 23:35:49 +09:00
Peter Evans
0ae1c4b014 Add action 2019-11-08 10:37:57 +09:00
Peter Evans
4d84287ffa Initial commit 2019-11-08 10:12:38 +09:00