alr-publish - Help with the publication of a new release
alr publish [options] [--skip-build] [--tar] [--manifest <file>]
[<URL> [commit]]]
- --manifest=ARG
- Selects a manifest file other than ./alire.toml
- --tar
- Start the publishing assistant to create a source archive
from a local directory
- --trusted-sites
- Print a list of trusted git repository sites
- --skip-build
- Skip the build check step
- -c, --config=ARG
- Override configuration folder location
- -f, --force
- Keep going after a recoverable troublesome situation
- -h, --help
- Display general or command-specific help
- -n, --non-interactive
- Assume default answers for all user prompts
- --no-color
- Disables colors in output
- --no-tty
- Disables control characters in output
- --prefer-oldest
- Prefer oldest versions instead of newest when resolving
dependencies
- --version
- Displays version and exits
- -q
- Limit output to errors
- -v
- Be more verbose (use twice for extra detail)
- -d, --debug[]
- Enable debug-specific log messages
Checks a release and generates an index manifest
See full details at
https://github.com/alire-project/alire/blob/master/doc/publishing.md URL is an
optional path to a remote source archive, or a local or remote git repository.
For the common use case of a github-hosted repository, issue `alr publish`
after committing and pushing the new release version. Use
--tar to
create a source archive ready to be uploaded. Use
--manifest to use
metadata in a non-default file. See the above link for help with other
scenarios.
alr(1),
alr-action(1),
alr-build(1),
alr-clean(1),
alr-dev(1),
alr-edit(1),
alr-run(1),
alr-test(1),
alr-exec(1),
gprbuild(1)
Generated with generate-man from Alire execution