Skip to content
You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?
type

GitHub Action

Notion release notes

v0.5

Notion release notes

type

Notion release notes

Creates a new page in an existing database to capture release notes

Installation

Copy and paste the following snippet into your .yml file.

              

- name: Notion release notes

uses: infinitaslearning/[email protected]

Learn more about this action in infinitaslearning/notion-release-notes

Choose a version

Notion Release Notes

This action allows you to specify an existing database in your Notion account that it can add a release note to within an action.

Typically used alongside https://github.com/mikepenz/release-changelog-builder-action

Notion integration and token

You need to have an integration access token - which you can get from https://www.notion.so/my-integrations after creating an integration.

Notion Database

This action expects a Notion database with the following properties:

Name: text Date: date Tags: tags

Note that you must share your database with the integration you created earlier to be able to access it!

It can look like this:

Screenshot 2021-12-18 at 08 55 42

And each actual page contains whatever your release notes are:

Screenshot 2021-12-18 at 08 56 44

Usage

Typically this is used with a changelog builder:

- name: Release Changelog Builder
    uses: mikepenz/[email protected]
    id: build_changelog
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}   
- name: Notion release notes        
  uses: infinitaslearning/notion-release-notes@main        
  with:          
    token: ${{ secrets.NOTION_TOKEN }}
    database: 619f0845c68a4c18837ebdb9812b90c0
    name: Release    
    tags: tag,comma,separated
    body: ${{ steps.build_changelog.outputs.changelog }}

To get the database ID, simply browse to it, click on the '...' and get a 'Copy link'. The GUID at the end of the URL is the id.

Development

Assumes you have @vercel/ncc installed globally. After changes ensure you npm run build, commit and then submit a PR.