Verify whether git credentials are working before deploying about monodeploy HOT 6 CLOSED

Makes sense to me. Any ideas how we can verify credentials? Should we do this in dry run as well?

And are you interested in contributing this feature? (If so, I can point you in the right direction)

from monodeploy.

ruin the 1.0.0 release of one of my monorepos

You have 72 hours to delete a release from npm.

https://docs.npmjs.com/unpublishing-packages-from-the-registry

from monodeploy.

I'd like to contribute, I glanced at the repository but I didn't spot the right place to do it fast enough to warrant making a pr before an issue :)

Semantic release does it by git push --dry-run, which some people on StackOverflow say does not work, but it does seem to work for me.

One of my repositories:

git push --dry-run --no-verify https://github.com/edielemoine/eslint.git HEAD:test

To https://github.com/edielemoine/eslint.git
 * [new branch]      HEAD -> test

A repository I can't push to:

git push --dry-run --no-verify https://github.com/eslint/eslint.git HEAD:test

remote: Permission to eslint/eslint.git denied to EdieLemoine.
fatal: unable to access 'https://github.com/eslint/eslint.git/': The requested URL returned error: 403

Should we do this in dry run as well?

I use dry run to check if my config works, so knowing I can't push commits before running a real deploy would be very useful.

You have 72 hours to delete a release from npm.

I know, but it doesn't allow you to republish the same name@version ever again :/

from monodeploy.

I glanced at the repository but I didn't spot the right place

All git commands live in this file https://github.com/tophat/monodeploy/blob/main/packages/git/src/gitCommands.ts which must also be duplicated in the mocks. You'd add a new command to verify push permissions.

The monodeploy pipeline is defined in this file: https://github.com/tophat/monodeploy/blob/main/packages/node/src/index.ts.

You could do the check in a stage before the publish to npm here:

The check should only run if config.git.push is true.

An alternative approach would be to run the "verify git permissions" check in place of the real git push when in dry run:

from monodeploy.

Thanks, just opened a pr! :)

from monodeploy.

Some enhancements in https://github.com/tophat/monodeploy/releases/tag/monodeploy%403.4.0

from monodeploy.