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

fix(Release): added a note to the release process readme #1632

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

davidkbh
Copy link
Collaborator

@davidkbh davidkbh commented Nov 4, 2024

Description

Two-pronged MR. Adds a note to help people avoid the mistake of a missing release, and triggers a release for styling fixes.

Verify that...

  • Any related demos were added and npm start and npm run build still works
  • New demos work in Safari, Chrome and Firefox
  • npm run lint passes
  • npm test passes and code coverage is increased
  • npm run build still works

Bullhorn Internal Developers

  • Run Novo Automation
Screenshots

Copy link
Contributor

github-actions bot commented Nov 4, 2024

Visit the preview URL for this PR (updated for commit d04c989):

https://novo-elements--pr1632-f-trigger-release-q0daamlo.web.app

(expires Mon, 11 Nov 2024 17:34:01 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: f1783e19c2444272095017dd8ba433fff0ee3f61

@davidkbh davidkbh merged commit 510623d into next Nov 4, 2024
6 checks passed
@davidkbh davidkbh deleted the f/trigger-release branch November 4, 2024 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants