sanity-plugin-dashboard-widget-github-environments v1.0.0
Sanity Dashboard Widget: GitHub Actions
This is a Sanity Studio v3 plugin.
Sanity Studio Dashboard Widget for triggering GitHub Actions.
Install
npm install --save sanity-plugin-dashboard-widget-github-actionsor
yarn add sanity-plugin-dashboard-widget-github-actionsEnsure that you have followed install and usage instructions for @sanity/dashboard.
Usage
Add it as a widget to @sanity/dashboard plugin in sanity.config.ts (or .js):
import {dashboardTool} from '@sanity/dashboard'
import {githubWidget} from 'sanity-plugin-dashboard-widget-github-actions'
export default defineConfig({
// ...
plugins: [
dashboardTool({
widgets: [
githubWidget({
title: 'My Netlify deploys',
sites: [
{
title: 'Sanity Studio',
apiId: 'xxxxx-yyyy-zzzz-xxxx-yyyyyyyy',
buildHookId: 'xxxyyyxxxyyyyxxxyyy',
name: 'sanity-gatsby-blog-20-studio',
},
{
title: 'Website',
apiId: 'yyyyy-xxxxx-zzzz-xxxx-yyyyyyyy',
buildHookId: 'yyyyxxxxxyyyxxdxxx',
name: 'sanity-gatsby-blog-20-web',
url: 'https://my-sanity-deployment.com',
},
],
}),
],
}),
],
})Widget options
title - Override the widget default title
sites[] - Your Netlify sites to show deploys for
apiId- The Netfliy API ID of your site (see Site Settings > General > Site Details > Site Information -> API ID).buildHookId- The id of a build hook you have created for your site within the Netlify administration panel (see Site Settings > Build & Deploy > Continuous Deployment -> Build Hooks).name- The Netlify site nametitle- Override the site name with a custom titleurl- Optionally override site deployment url. By default it is inferred to behttps://netlify-site-name.netlify.app.branch- Optionally pass the name of a branch to deploy
License
MIT-licensed. See LICENSE.
Develop & test
This plugin uses @sanity/plugin-kit with default configuration for build & watch scripts.
See Testing a plugin in Sanity Studio on how to run this plugin with hotreload in the studio.
Release new version
Run "CI & Release" workflow. Make sure to select the main branch and check "Release new version".
Semantic release will only release on configured branches, so it is safe to run release on any branch.
2 years ago