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
When we release new version, it should be automatically reflected in both pkg.go.dev & go report card.
I think we should create github action workflow that will be triggered whenever we release a new version. After that, the workflow will do the following:
Refresh pkg.go.dev by using this HTTP request (remember to change the version to the version released):
When we release new version, it should be automatically reflected in both pkg.go.dev & go report card.
I think we should create github action workflow that will be triggered whenever we release a new version. After that, the workflow will do the following:
Refresh pkg.go.dev by using this HTTP request (remember to change the version to the version released):
When we release new version, it should be automatically reflected in both
pkg.go.dev
& go report card.I think we should create github action workflow that will be triggered whenever we release a new version. After that, the workflow will do the following:
Refresh
pkg.go.dev
by using this HTTP request (remember to change the version to the version released):Refresh go report card by using this HTTP request:
When we release new version, it should be automatically reflected in both
pkg.go.dev
& go report card.I think we should create github action workflow that will be triggered whenever we release a new version. After that, the workflow will do the following:
Refresh
pkg.go.dev
by using this HTTP request (remember to change the version to the version released):Refresh go report card by using this HTTP request:
Note:
For go report card, if we have more than one change within 24 hours, the latest changes will be reflected after 24 hours. Just beware of this.
For go report card, if we have more than one changes within 24 hours, the latest changes will be reflected after 24 hours. Just beware of this.
The text was updated successfully, but these errors were encountered: