⚫ To use GitHub Actions for CI/CD.
🟠 To have public + private projects using private secrets here, with some secrets being automatically rotated.
🔴 Any projects that need to be deployed are actually deployed to a personal AWS account.
🟢 To use GitHub Templates as away of enforcing consistantcy across most repositories.
🔵 To create custom `GitHub Actions` to handle "standard" workflows.
> (i.e. posting to Slack, linting, templating, etc.)
🟣 Writing most things from scratch, unless an offical "thing" is provided that can be trusted.
> (i.e. like a `GitHub Action` for authing to an AWS account, posting to Slack, etc.)
Pinned Loading
Repositories
Showing 10 of 11 repositories
- determine-workflow-conclusion Public
🐋 A GitHub Action for determining the status of a workflow when run inside a pipeline. Largely used to post workflow statuses to Slack via https://github.com/jmpa-io/post-to-slack.
jmpa-io/determine-workflow-conclusion’s past year of commit activity - post-to-slack Public
🐋 A GitHub Action for sending notifications from running jobs to Slack (via a given webhook).
jmpa-io/post-to-slack’s past year of commit activity - pipelines Public
🌱 A monorepo used to store org-wide resources used by other repositories in this org, such as pipelines, scripts, mechanisms to deploy, and templates. Used in conjunction with https://github.com/jmpa-io/root-template.
jmpa-io/pipelines’s past year of commit activity - jmpa-theme Public Forked from apvarun/digital-garden-hugo-theme
The hugo theme for https://jmpa.io. Built upon https://github.com/apvarun/digital-garden-hugo-theme.
jmpa-io/jmpa-theme’s past year of commit activity