KO
|
EN
gitlite โ search
Search
#javascript
#python
#hacktoberfest
#react
#ai
#typescript
#llm
#go
#golang
#android
#machine-learning
#rust
#deep-learning
#linux
gh-workflow-gen
โ 11
Open GitHub โ
Generate GitHub Workflows
Download README (.md)
Explore Similar Repositories
equi_q_corl21
:
This repository contains the code of the paper Equivariant Q Learning in Spatial Action Spaces
tama-sailfish-waydroid-instructios
:
Instructions to run Waydroid on Sony Tama devices running Sailfish OS.
LN_MysteryRogueSystem
:
No description available.
yubikey-companion
:
One-click input of totp codes from your Yubikey
yarn-berry-example
:
Yarn ๐งถ berry zero-installs example ๐ญ using react + typescript + cypress + jest + github actions CI/CD + github pages
// repository documentation
Was this content helpful?
โ 0
(0 ratings)
Select Rating:
โ
โ
โ
โ
โ
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
gh-workflow-gen
?
Download (.md)
# GitHub Workflow Generator Declare your GitHub Workflows in TypeScript or JavaScript instead of YAML! [](https://www.npmjs.com/package/@wardellbagby/gh-workflow-gen) [](https://github.com/wardellbagby/gh-workflow-gen/blob/main/LICENSE.md) [](https://github.com/wardellbagby/gh-workflow-gen/actions?query=workflow%3A%22Run+all+tests%22) ## What is it? Github Workflow Generator is a library that enables you to write templates for your GitHub Workflows in JavaScript or Typescript and use that code to generate valid GitHub Workflows as YAML files. Admittedly, that's a long and complex sentence, so let's show a quick example instead: ```typescript const workflow: Workflow = { name: "Simple Workflow", on: { push: {}, }, jobs: { echo: { name: "Echo", "runs-on": "macos-latest", steps: [ { name: "Echoing!", run: 'echo "Hello World!"', }, ], }, }, }; ``` This will generate this Yaml file: ```yaml name: 'Simple Workflow' 'on': push: {} jobs: echo: name: 'Echo' runs-on: 'macos-latest' steps: - name: 'Echoing!' run: 'echo "Hello World!"' ``` This Workflow will run on every new push to any branch, with a single job named "Echo" that runs on a macOS 10.15 runner that prints out "Hello World". ## I understand it, but why do I want this library? If your Workflow is as simple as the Workflow listed above, you likely wouldn't want or need this library. However, if you have multiple Workflows that need to share steps, this library becomes very useful. Imagine: ```typescript const basicSetup: Step[] = [ { name: "Checkout project", uses: 'actions/checkout@v2', }, { name: "Install project dependencies", run: "npm ci", }, ]; const buildAppWorkflow: Workflow = { name: "Build The App", on: { push: {}, }, jobs: { echo: { name: "Build", "runs-on": "macos-latest", steps: [ ...basicSetup, { name: "Build", run: 'npm run build', }, ], }, }, }; const buildLibraryWorkflow: Workflow = { name: "Build The Library", on: { push: { branches: ['special-branch'] }, }, jobs: { echo: { name: "Build", "runs-on": "ubuntu-latest", steps: [ ...basicSetup, { name: "Build", run: 'npm run build-lib', }, ], }, }, }; ``` This is only a small taste as well. You can share whole jobs, if needed. ### What's this I hear about easier versioning for my actions? Sounds cool! Since everything is strongly-typed using TypeScript, you can also enforce that every Workflow uses the same version of your various actions, and update all of your actions at the same time. [See the "using versions" example here.](examples/using%20versions/) ### Any other neat things I can do? Good question! Since this library doesn't currently exhaustively cover everything you can do in a Workflow, the type system has been purposefully made to be easily extensible, where possible. [Take a look at the "adding or modifying fields" example for how to do that.](examples/adding%20or%20modifying%20fields/) ### You talk a lot about TypeScript, but I prefer JavaScript. Can I still use this library? Yup! Consider the typings just a bit of syntactical sugar; this library works just fine with pure JavaScript as well. ## So cool! How do I set this up for my project?! First, let's install it: ```shell npm install --save-dev @wardellbagby/gh-workflow-gen ``` Next, let's create our first Workflow: ```typescript import { Workflow } from '@wardellbagby/gh-workflow-gen'; export const myWorkflow: Workflow = { // TODO fill this in. } ``` Now, we need to create a simple script to import these Workflows and write them to a file. ```typescript import { myWorkflow } from "myWorkflowFile"; import { writeWorkflow } from "@wardellbagby/gh-workflow-gen"; writeWorkflow(myWorkflow); ``` Lastly, we simply run the script you just created in the root of your project folder. ```shell cd path/to/my/project node generate_workflows.js ``` This will create the `workflows` directory inside your existing `.github` directory with the generated Workflows saved. ### That setup is...complex. Any other examples? Yes! This project uses itself, and as a part of its setup, it uses [script created in the last step above](scripts/generate_workflows.ts) and runs as a pre-commit hook using Husky. If you'd like that as an example, [check this out.](.husky/pre-commit)
