You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please consider changing testify release process so new releases will be visible from repository Github releases page. Seeing latest version date at the right side of the repository landing page in Github is useful.
Currently these pages are quite different. If you are used to check releases page the current version then what you would see is quite different what tags page shows.
It does not need to contain fancy changelog or changelog at all.
This is what I see at the moment - almost 2 years old release:
The text was updated successfully, but these errors were encountered:
Create github workflow action (https://github.com/softprops/action-gh-release) that creates new release when new tag is pushed. This way current testify maintainer/author do not need to change their habbits - this action will kick in on matching tag push.
Workflow file:
name: release on new tag# this flow will be run only when new tags are pushed that match our patternon:
push:
tags:
- "v[0-9]+\.[0-9]+\.[0-9]+"jobs:
build:
runs-on: ubuntu-lateststeps:
- name: Checkoutuses: actions/checkout@v3
- name: Create releaseuses: softprops/action-gh-release@v1
Please consider changing testify release process so new releases will be visible from repository Github releases page. Seeing latest version date at the right side of the repository landing page in Github is useful.
https://github.com/stretchr/testify/releases
https://github.com/stretchr/testify/tags
Currently these pages are quite different. If you are used to check releases page the current version then what you would see is quite different what tags page shows.
It does not need to contain fancy changelog or changelog at all.
This is what I see at the moment - almost 2 years old release:
![image](https://user-images.githubusercontent.com/2320301/202391238-5695d7c5-9230-4d06-9f95-339473e791cc.png)
The text was updated successfully, but these errors were encountered: