https://github.com/endbug/export-label-config

An action that lets you generate a file containing your label settings for the current repo
https://github.com/endbug/export-label-config

actions config export github hacktoberfest labels repository sync workflow

Last synced: 27 days ago
JSON representation

An action that lets you generate a file containing your label settings for the current repo

• Host: GitHub
• URL: https://github.com/endbug/export-label-config
• Owner: EndBug
• License: mit
• Created: 2020-10-11T10:26:32.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2024-09-03T20:09:07.000Z (2 months ago)
• Last Synced: 2024-10-15T13:06:20.622Z (about 1 month ago)
• Topics: actions, config, export, github, hacktoberfest, labels, repository, sync, workflow
• Language: TypeScript
• Homepage:
• Size: 418 KB
• Stars: 2
• Watchers: 2
• Forks: 3
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Export label config

You can use this action to generate a JSON or YAML file that contains the current label config of one of your repositories.  

This is made with the [EndBug/label-sync](https://github.com/EndBug/label-sync) action in mind, but you can use that data with whatever tool you prefer.

### Example workflow:

```yaml

name: Export label config

on: 

  # You can run this with every event, but it's better to run it only when you actually need it.

  workflow_dispatch:

jobs:

  labels:

    runs-on: ubuntu-latest

    steps:

      - uses: EndBug/export-label-config@v1

        with:

          # This is needed if you're dealing with private repos.

          token: ${{ secrets.GITHUB_TOKEN }}

          # Set this to `true` if you want to get the raw API reponse. Defaults to `false`.

          raw-result: false

          # By default every label entry will have an `aliases` property set to an empty array.

          # It's for EndBug/label-sync, if you don't want it you cans set this to `false`

          add-aliases: true

```

After running your workflow, you'll find the genearted files in the "Artifacts" section of your run.  

To find more about artifacts, please refer to the [GitHub Docs](https://docs.github.com/en/free-pro-team@latest/actions/guides/storing-workflow-data-as-artifacts#about-workflow-artifacts).