GitShow/thedaviddias/publish-release-info-action
thedaviddias

publish-release-info-action

Sends release information to Slack keeping your team up-to-date with the latest releases

by thedaviddias
actionsgithub-actionsslackworkflow
Star on GitHubForknpm

TypeScript

13 stars2 forks3 contributorsQuiet · 2y agoSince 2023v3.3.0MIT

Meet the team

See all 3 on GitHub →
thedaviddias
thedaviddias17 contributions
dependabot[bot]Bot
dependabot[bot]2 contributions

Languages

View on GitHub →
TypeScript99%
JavaScript0.9%
Shell0.1%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

3 of 6 standards met

Community profile →
85
✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · Last activity 2y ago
See all on GitHub →
jonashaag
Does not fetch correct tagsOpenIssue

Describe the bug** We have tags We recently changed to calendar versioning. Now on an update, the action fetches these tags: v0.1.22 v0.1.23 and publishes release info based on v0.1.23. But the actual latest tags according to the release date is 25.02.13.

jonashaag · 1y ago
ScottMacDougall
Slack call fails with 'invalid_blocks' when PR content exceeds 3000 charactersOpenIssue

Describe the bug** This is a hypothesis, but according to the Slack API, section blocks have a limit of 3000 characters for the field (source). We often have a large number of PR's in a release, but our slack call often fails, and this seems to be the most likely reason for it. Possible solutions: 1. Provide an option to not emit PR titles in the slack message 2. Do a hard cut at 3000 characters, possibly with an indication that there are overflow PRs 3. Split the PR list string into chunks, each being

ScottMacDougall · 1y ago
makandz
Wrong user being reported under "created by"OpenIssue

Describe the bug When a release was made by someone that wasn't part of the changelog, the "Created by" name was marked as the person in the changelog rather than the person triggering the release. To Reproduce Steps to reproduce the behavior: 1. Make a release that has 1 change by person A, have person B trigger the release 2. You will notice "Created by" says person A Expected behavior** It should be "Created by" person B, the one that triggered the release.

makandz · 1y ago
Structured data for AI agents

Repository: thedaviddias/publish-release-info-action. Description: Sends release information to Slack keeping your team up-to-date with the latest releases Stars: 13, Forks: 2. Primary language: TypeScript. Languages: TypeScript (99%), JavaScript (0.9%), Shell (0.1%). License: MIT. Topics: actions, github-actions, slack, workflow. Latest release: v3.3.0 (3y ago). Open PRs: 12, open issues: 4. Last activity: 2y ago. Community health: 85%. Top contributors: thedaviddias, dependabot[bot].

·@ofershap

Replace github.com with gitshow.dev