Skip to content

add ci run to vnext - #126

Merged
VisualBean merged 1 commit into
vnextfrom
main
Sep 8, 2023
Merged

VisualBean merged 1 commit into
vnextfrom
main

Conversation

@VisualBean

Copy link
Copy Markdown
Contributor

No description provided.

@VisualBean
VisualBean merged commit 81658d4 into vnext Sep 8, 2023
@github-actions github-actions Bot added the ci/cd label Sep 8, 2023
@github-actions

github-actions Bot commented Sep 8, 2023

Copy link
Copy Markdown

We require all PRs to follow Conventional Commits specification.
More details 👇🏼

 No release type found in pull request title "add ci run to vnext". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant