Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: removing pr-release workflow #3653

Merged
merged 2 commits into from
Jan 31, 2025

Conversation

arboleya
Copy link
Member

Summary

Only proper tags should be published from now on.

Checklist

  • All changes are covered by tests (or not applicable)
  • All changes are documented (or not applicable)
  • I reviewed the entire PR myself (preferably, on GH UI)
  • I described all Breaking Changes (or there's none)

@arboleya arboleya added the chore Issue is a chore label Jan 31, 2025
@arboleya arboleya self-assigned this Jan 31, 2025
Copy link

vercel bot commented Jan 31, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
fuels-template ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2025 11:45am
ts-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2025 11:45am
ts-docs-api ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2025 11:45am

@arboleya arboleya changed the title chore: removing ways for releasing non-tagged work-trees chore: removing pr-release workflow Jan 31, 2025
@Torres-ssf Torres-ssf enabled auto-merge (squash) January 31, 2025 11:32
Copy link
Contributor

Coverage Report:

Lines Branches Functions Statements
77.07%(+0%) 70.72%(+0%) 75.17%(+0%) 77.07%(+0%)
Changed Files:

Coverage values did not change👌.

@Torres-ssf Torres-ssf merged commit b7ecfa5 into master Jan 31, 2025
24 checks passed
@Torres-ssf Torres-ssf deleted the aa/chore/removing-pr-release-workflow branch January 31, 2025 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Issue is a chore
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants