Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

im-open / git-version-lite Public

generated from im-open/javascript-action-template

Notifications You must be signed in to change notification settings
Fork 8
Star 2

Code
Issues
Pull requests 1
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Build and Review PR

Build and Review PR #50 #85

Sign in to view logs

Sign in to view logs

Build and Review PR #50

Build and Review PR #50 #85

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

12 errors and 2 warnings

The job was canceled because "_13_major_BREAKING_CHANGE" failed.

Then the outputs should contain the next major version which includes the branch name in NEXT_VERSION

Process completed with exit code 1.

And the outputs should be the next major version

Process completed with exit code 1.

When a pre-release version is requested from git-version-lite

An error occurred calculating the next pre-release version: Failed running git.

And the environment variables should be the next major version

Process completed with exit code 1.

And the environment variables should contain the next major version which includes the branch name in NEXT_VERSION

Process completed with exit code 1.

Setup - Add commit to a branch that coincides with major changes

Process completed with exit code 128.

Then the outcome should be success

Process completed with exit code 1.

Setup - Checkout testing repo in the root directory

repository 'https://github.com/im-open/internal-repo-for-testing-purple-actions/' not found

Setup - Checkout testing repo in the root directory

repository 'https://github.com/im-open/internal-repo-for-testing-purple-actions/' not found

Setup - Checkout testing repo in the root directory

repository 'https://github.com/im-open/internal-repo-for-testing-purple-actions/' not found

Setup - Checkout testing repo in the root directory

The process '/usr/bin/git' failed with exit code 128

When a pre-release version is requested from git-version-lite

There do not appear to be any tags on the repository. If that is not accurate, ensure fetch-depth: 0 is set on the checkout action.

When a release version is requested from git-version-lite

There do not appear to be any tags on the repository. If that is not accurate, ensure fetch-depth: 0 is set on the checkout action.

test-incrementing (14, major, BREAKING CHANGE - removing input c, 2.0.0, 2.0, 2)

test-incrementing (14, major, BREAKING CHANGE - removing input c, 2.0.0, 2.0, 2)

cancelled Feb 10, 2025 in 37s

Loading

Re-running jobs...

You can’t perform that action at this time.