act-bin 0.2.68__py3-none-win_amd64.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Binary file
@@ -0,0 +1,37 @@
1
+ Metadata-Version: 2.1
2
+ Name: act-bin
3
+ Version: 0.2.68
4
+ Summary: Run your GitHub Actions locally 🚀
5
+ Keywords: github,actions,act
6
+ Author-Email: dowon <ks2515@naver.com>
7
+ License: MIT
8
+ Classifier: Programming Language :: Go
9
+ Classifier: License :: OSI Approved :: MIT License
10
+ Classifier: Intended Audience :: Developers
11
+ Classifier: Topic :: Software Development :: Build Tools
12
+ Classifier: Topic :: Software Development :: Testing
13
+ Project-URL: repository, https://github.com/Bing-su/pip-binary-factory
14
+ Project-URL: act, https://nektosact.com
15
+ Requires-Python: >=3.8
16
+ Description-Content-Type: text/markdown
17
+
18
+ # act-bin
19
+
20
+ https://nektosact.com
21
+
22
+ https://github.com/nektos/act
23
+
24
+ > "Think globally, `act` locally"
25
+
26
+ Run your [GitHub Actions](https://developer.github.com/actions/) locally! Why would you want to do this? Two reasons:
27
+
28
+ - **Fast Feedback** - Rather than having to commit/push every time you want to test out the changes you are making to your `.github/workflows/` files (or for any changes to embedded GitHub actions), you can use `act` to run the actions locally. The [environment variables](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#filesystems-on-github-hosted-runners) are all configured to match what GitHub provides.
29
+ - **Local Task Runner** - I love [make](<https://en.wikipedia.org/wiki/Make_(software)>). However, I also hate repeating myself. With `act`, you can use the GitHub Actions defined in your `.github/workflows/` to replace your `Makefile`!
30
+
31
+ # How Does It Work?
32
+
33
+ When you run `act` it reads in your GitHub Actions from `.github/workflows/` and determines the set of actions that need to be run. It uses the Docker API to either pull or build the necessary images, as defined in your workflow files and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. The [environment variables](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#file-systems) are all configured to match what GitHub provides.
34
+
35
+ Let's see it in action with a [sample repo](https://github.com/cplee/github-actions-demo)!
36
+
37
+ ![Demo](https://raw.githubusercontent.com/wiki/nektos/act/quickstart/act-quickstart-2.gif)
@@ -0,0 +1,6 @@
1
+ act_bin-0.2.68.data/scripts/act.exe,sha256=RbB4T4Q7cjKYXuUu0rxtIL2I-lzb7fiUuWkdX4_f0qA,19937280
2
+ act_bin-0.2.68.dist-info/METADATA,sha256=b_FEo9Bw4SkUhDT7qeAMVI0WhGh-Gvb6QhiQugEQepY,2642
3
+ act_bin-0.2.68.dist-info/WHEEL,sha256=_8cbh4lKJDHWCMsabvc_a8gcwSeChpwM8ul3bhUn2L8,97
4
+ act_bin-0.2.68.dist-info/entry_points.txt,sha256=6OYgBcLyFCUgeqLgnvMyOJxPCWzgy7se4rLPKtNonMs,34
5
+ act_bin-0.2.68.dist-info/licenses/LICENSE,sha256=cwXWhokxNQvza-dovSEhXqp2jD5LfD7vGCJ0I7tbtS4,1073
6
+ act_bin-0.2.68.dist-info/RECORD,,
@@ -0,0 +1,4 @@
1
+ Wheel-Version: 1.0
2
+ Generator: pdm-backend (2.4.3)
3
+ Root-Is-Purelib: false
4
+ Tag: py3-none-win_amd64
@@ -0,0 +1,4 @@
1
+ [console_scripts]
2
+
3
+ [gui_scripts]
4
+
@@ -0,0 +1,22 @@
1
+
2
+ The MIT License (MIT)
3
+
4
+ Copyright (c) 2024 Dowon
5
+
6
+ Permission is hereby granted, free of charge, to any person obtaining a copy
7
+ of this software and associated documentation files (the "Software"), to deal
8
+ in the Software without restriction, including without limitation the rights
9
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10
+ copies of the Software, and to permit persons to whom the Software is
11
+ furnished to do so, subject to the following conditions:
12
+
13
+ The above copyright notice and this permission notice shall be included in all
14
+ copies or substantial portions of the Software.
15
+
16
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
22
+ SOFTWARE.