orhun/git-cliff
1
1
Fork 0
mirror of https://github.com/orhun/git-cliff.git synced 2024-11-22 08:24:58 +03:00
Code Issues Projects Releases Wiki Activity
main
git-cliff/.dockerignore

24 lines
386 B
Plaintext
Raw Permalink Normal View History

chore(docker): add Dockerfile
2021-06-11 21:41:03 +03:00
# Directories
/.git/
/.github/
chore(npm): package `git-cliff` for npm (#133) * chore: scaffold a typescript node project * feat: execute git cliff binary using nodejs * fix: process doesnt return status code * fix: optional dependencies are not added to git-cliff * chore(npm): move NPM package to npm folder * chore(docker): add NPM package to .dockerignore * feat(cd): publish NPM package via continuous deployment workflow * docs: add npm instructions to README * chore(npm): update package keywords * chore(cd): publish the NPM package publicly * style(readme): update NPM section in README.md Co-authored-by: Burak Güner <burak.guner@callstack.com> Co-authored-by: Burak Güner <md.burak.guner@gmail.com>
2023-01-09 17:12:22 +03:00
/npm/
chore(pypi): publish `git-cliff` on PyPI (#158) * chore(pypi): First shot at PyPi publishing * docs(pypi): Draft docs for install from PyPI * fix(pypi): fix spellig mistake and add missing dependency * chore(pypi): rc1 for pypi publish workflow * docs(pypi): add example for pip install command Also tweaked verbiage a little * fix(docs): remove extra backtick in command example * fix(pypi): fix MATURIN_REPOSITORY definition * chore(pypi): rc2 for pypi publish fixes mistake in use of endsWith and startsWith expression syntax. Thanks https://rhysd.github.io/actionlint/! * chore(pypi): rc3 for pypi publish workflow Changes: - fixes an error with maturin build - makes sure maturin commands are run in directory containing pyproject.toml - manifest path is now specified in pyproject.toml - sdist is now created as a part of the build command * fix(pypi): specify cwd in action arg * fix(pypi): fix various path issues * chore(docker): ignore pypi directory --------- Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2023-08-16 10:53:31 +03:00
/pypi/
chore(website): move website to website folder This reverts commit b6e52e128e7a105682adf885850d14deefdff3ec.
2023-04-09 18:16:31 +03:00
/website/
chore(docker): add Dockerfile
2021-06-11 21:41:03 +03:00
# Files
.editorconfig
.gitignore
*.md
codecov.yml
Dockerfile
LICENSE
rustfmt.toml
chore(docker): add Jekyll configuration to .dockerignore
2022-12-26 19:52:06 +03:00
_config.yml
chore(ci): update the link checker configuration (#315) * chore(lychee): update link checker configuration * refactor(ci): provide GitHub token * refactor(ci): set a custom GitHub token * fix(ci): set concurrency for checking links * chore(ci): ignore more sites for lychee * chore(ci): update lychee ignore list --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2023-10-14 19:22:29 +03:00
.lycheeignore
feat(docker): build arm64 images again (#879) (#919) * chore(docker): ignore rust toolchain in docker builds This commit adds the known names of the rust-toolchain files to the .dockerignore file. This has two reasons why it makes sense: - The initial docker layer already has a set up rust toolchain that is sufficient to build the project. Thus, by providing a toolchain file, the toolchain would be installed again during docker build. - Currently cargo-chef only copies the toolchain files during cooking but it gets not used during the building of the dependencies in the cook call, see https://github.com/LukeMathWalker/cargo-chef/issues/271. With this in mind, currently the dependencies were actually build twice. Once with the installed toolchain from the image itself, and then in the actual cargo build call with the toolchain speciefied in the toolchain file. Building them twice resulted in timeouts when building the arm64 images as they are emulated using qemu, which is itself already slower than building natively. Now one could argue, that as soon as the mentioned issue is solved using the toolchain again would be fine. But then it would be still needed to assemble the Dockerfile in a way that the toolchain is not build twice. Because the current structure of the Dockerfile builds the toolchain once in the cargo-chef prepare step and once during the cargo build step (and would later build it during the cargo-chef cook instead of cargo build). With all this in mind using no toolchain file but instead just using the sufficient rust installation from the base image makes sense. * Revert "chore(docker): disable building arm64 docker images temporarily (#879)" This reverts commit cde2a8e3222f5e8f8bdd9ae841fd0e5c42f68846. Commit 73f75d5289cb782f42b6b71b84c03b56e4833b0a made it possible to build the arm64 image again without running into timeouts.
2024-10-17 11:05:05 +03:00
# Ignore rust toolchain files as they would needlessly fetch the toolchain.
# But the image already contains a sufficient toolchain.
# Ignore both the latest naming and the legacy naming
rust-toolchain.toml
rust-toolchain
Reference in New Issue Copy Permalink