Coder Social home page Coder Social logo

Comments (4)

RomanHotsiy avatar RomanHotsiy commented on August 10, 2024

Hi @stefanullinger,

I'm not sure why it fails (would be great if you let me know the error message) but I guess it may be fixed with --allow-empty flag for git commit

Your PR would be appreciated!

from branch-release.

stefanullinger avatar stefanullinger commented on August 10, 2024

Hi @RomanHotsiy,

it looks something like this:

`> branch-release -s build

set -e
exec git stash
No local changes to save
exec git show HEAD:package.json { silent: true }
exec git ls-remote -t origin { silent: true }
set +e
exec git fetch --unshallow
fatal: --unshallow on a complete repository does not make sense
set -e
rm -rf dist
exec git ls-remote -h origin { silent: true }
exec git fetch -f origin releases:releases
exec git checkout releases
Switched to branch 'releases'
exec git merge -X theirs @{-1}
Merge made by the 'recursive' strategy.
package.json | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
exec npm run-script build

[email protected] build /Users/stefan/Documents/Development/media-library-starter-template
n-clean ./dist/ && rollup -c rollup.config.js && rollup -c rollup.config.prod.js

sources/index.ts → ./dist/mediaLibrary.js...
created ./dist/mediaLibrary.js in 1.1s

sources/index.ts → ./dist/mediaLibrary.min.js...
created ./dist/mediaLibrary.min.js in 1.3s
exec git add dist -f
warning: CRLF will be replaced by LF in dist/index.d.ts.
The file will have its original line endings in your working directory.
warning: CRLF will be replaced by LF in dist/mediaLibrary.js.
The file will have its original line endings in your working directory.
warning: CRLF will be replaced by LF in dist/mediaLibraryModule.d.ts.
The file will have its original line endings in your working directory.
warning: CRLF will be replaced by LF in dist/mediaLibraryService.d.ts.
The file will have its original line endings in your working directory.
exec git commit -m "Release v1.0.1"
On branch releases
nothing to commit, working tree clean
exec: internal error
exec git reset --hard
HEAD is now at c072282 Merge branch 'master' into releases
exec git checkout @{-1}
Your branch is up-to-date with 'origin/master'.
Switched to branch 'master'
exec git stash pop
No stash found.
/Users/stefan/Documents/Development/media-library-starter-template/node_modules/shelljs/src/common.js:417
if (config.fatal) throw e;
^

Error: exec: internal error
at Object.error (/Users/stefan/Documents/Development/media-library-starter-template/node_modules/shelljs/src/common.js:128:27)
at _exec (/Users/stefan/Documents/Development/media-library-starter-template/node_modules/shelljs/src/exec.js:292:12)
at /Users/stefan/Documents/Development/media-library-starter-template/node_modules/shelljs/src/common.js:350:23
at switchBack (/Users/stefan/Documents/Development/media-library-starter-template/node_modules/branch-release/index.js:50:3)
at branchRelease (/Users/stefan/Documents/Development/media-library-starter-template/node_modules/branch-release/index.js:37:5)
at main (/Users/stefan/Documents/Development/media-library-starter-template/node_modules/branch-release/index.js:20:3)
at Object. (/Users/stefan/Documents/Development/media-library-starter-template/node_modules/branch-release/index.js:116:3)
at Module._compile (internal/modules/cjs/loader.js:805:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:816:10)
at Module.load (internal/modules/cjs/loader.js:672:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] release: branch-release -s build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/stefan/.npm/_logs/2019-06-25T05_59_01_157Z-debug.log`

from branch-release.

RomanHotsiy avatar RomanHotsiy commented on August 10, 2024

Looks like the root cause is:

nothing to commit, working tree clean
exec: internal error

so --allow-empty flag for git commit should help

from branch-release.

stefanullinger avatar stefanullinger commented on August 10, 2024

Alright, that's what I also found out. Then I will try to add the --allow-empty flag next week.

Thank you!

from branch-release.

Related Issues (2)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.