Search Results for "as-project"

Ensures you are publishing from your release branch (main and master by default). Ensures the working directory is clean and that there are no unpulled changes. Reinstalls dependencies to ensure your project works with the latest dependency tree. Ensures your Node.js and npm versions are supported by the project and its dependencies. Bumps the version in package.json and npm-shrinkwrap.json (if present) and creates a git tag. Prevents accidental publishing of pre-release versions under the latest dist-tag. Publishes the new version to npm, optionally under a dist-tag. ...

...Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary shell tasks with a list of staged files as an argument, filtered by a specified glob pattern. Linter commands work on a subset of all staged files, defined by a glob pattern. lint-staged uses micromatch for matching files. ...

Open source content management for your Git workflow. Use Netlify CMS with any static site generator for a faster and more flexible web project. Get the speed, security, and scalability of a static site, while still providing a convenient editing interface for content. Content is stored in your Git repository alongside your code for easier versioning, multi-channel publishing, and the option to handle content updates directly in Git. Netlify CMS is built as a single-page React app. ...

...A git hook is a command or script that is going to be run every time you perform a git action, like git commit or git push. If the execution of a git hook fails, then the git action aborts. For example, if you want to run linter on every commit to ensure code quality in your project, then you can create a pre-commit hook that would call npx lint-staged. Check out lint-staged. It works really well with simple-git-hooks. You can look up about git hooks on the Pro Git book. simple-git-hooks works well for small-sized projects when you need quickly set up hooks and forget about it. However, this package requires you to manually apply the changes to git hooks. ...

...When you're working in a Commitizen-friendly repository, you'll be prompted to fill in any required fields, and your commit messages will be formatted according to the standards defined by project maintainers. Installing and running Commitizen locally allows you to make sure that developers are running the exact same version of Commitizen on every machine.

...Results are filtered out if there were never any commits pushed on the main branch since the fork was created. This is meant to help increase the discoverability of useful forks of open-source projects. Sometimes, a project might be abandoned, or someone had a different idea of how it should be implemented... and when you go looking for those interesting forks, you find yourself searching through potentially hundreds of them. This tool is here to help you discover the hidden jewels you were looking for!

...It integrates with the popular commitizen ecosystem so that when you run npx git-cz or similar, you are prompted through a workflow instead of free-form message. The project emphasises consistency and readability in commit history, helping teams enforce semantic or conventional commit message formats. It supports custom configuration (for example via a changelog.config.js file) so you can adapt the prompts or types to your project’s conventions. Because it is open source (licensed under Unlicense) it can be freely integrated within CI pipelines or commit hooks to standardise message formats.

...meta is powered by plugins that wrap common commands, letting you execute them against some or all of the repos in your solution at once. meta is built on loop, and as such inherits loops ability to easily target a particular set of directories for executing a common command (eg meta git status --include-only dir1,dir2. See loop for more available options). meta is a tool for managing multi-project systems and libraries. It answers the conundrum of choosing between a mono repo or many repos by saying "both", with a meta repo! Give every engineer on your team the same project setup, regardless of where it's cloned. Execute arbitrary commands against many repos to manage your projects. Easily wrap commands for working with any platform, not just Node!

Asynchronous native Node bindings to libgit2. NodeGit will work on most systems out-of-the-box without any native dependencies. If you receive errors about libstdc++, which are commonly experienced when building on Travis-CI, you can fix this by upgrading to the latest libstdc++-4.9. If you wish to help contribute to NodeGit it is useful to build locally. If you encounter errors, you most likely have not configured the dependencies correctly. You will need libpcre, libpcreposix, libkrb5,...

...Please install it under the devDependencies section of your package.json. Please also note, that it is absolutely not advised to install ghooks globally. To work as expected, make it a development dependency of your project(s). Add a config.ghooks entry in your package.json and simply specify which git hooks you want and their corresponding commands. The hooks' working directory is relative to the git root (where you have your .git directory). This means that if your package.json is in a subdirectory of your git repository, you'll need to cd into the directory before running any npm scripts.