Skip to content

Commit

Permalink
Fix metadata workflow
Browse files Browse the repository at this point in the history
  • Loading branch information
@richardreeve
richardreeve committed Jul 21, 2024
1 parent b1a15ae commit b2a86ea
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions .github/workflows/metadata.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,19 +3,20 @@ name: Metadata and hygene
on:
push:
branches:
- dev
- main
tags:
- 'v*'
pull_request:
workflow_dispatch:

permissions: # needed to allow julia-actions/cache to proactively delete old caches that it has created
actions: write
contents: read

jobs:
metadata:
name: RSMD - ${{ github.event_name }}
timeout-minutes: 60
permissions: # needed to allow julia-actions/cache to proactively delete old caches that it has created
actions: write
contents: read
runs-on: ubuntu-latest
steps:
- name: Checkout code
Expand Down

2 comments on commit b2a86ea

@richardreeve
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/111455

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.2.5 -m "<description of version>" b2a86ea9a357bc6215f0c31cde46d56aa318424b
git push origin v0.2.5

Please sign in to comment.