Open Source JavaScript Version Control Software - Page 3

Der Werkplaner ist eine LAN-basierte Projektmanagement-Software für Architekturbüros und selbstständige Architekten. Sie integriert Dokumenten-, Adress-, Aufgaben- und Stundenzettelverwaltung entlang der Leistungsphasen gemäß Honorarordnung (LPH).

Comic Creation CMS will be an integrated CMS/Groupware/Portal webapplication for creating Comics/Graphic Novels fit for web and electronic publishing. Ambitions also to create an generic XML file format for active multimedia content comics (and more...)

Yet Another Tasks Manager?

Simple git hooks. It is not advised to install ghooks as a production dependency, as it will install git hooks in your production environment as well. 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.

git-cz is a command-line tool designed to guide developers in writing structured, conventional commits. Rather than manually typing commit messages, this tool prompts you to select commit types, scopes, and write descriptions according to a defined format. 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.

git peek is the fastest way to open a remote git repository in your local text editor. Use it when you want to browse or search other people's code with your own editor. Pass git peek a git repository or a github link, and it will quickly fetch and open it in your local editor. It stores the repository in a temporary directory and deletes it when you close the editor or git peek. If you don't pass git peek input, it will let you search Github repositories and show trending repositories. If you paste a link to a file on GitHub, it will quickly open the file in your local editor. If you pass it a GitHub repository, it fetches a tarball instead of using git and decompresses it while downloading it (streaming). From unscientific benchmarks, this is about 2x faster than cloning. While downloading & decompressing the tarball, it also downloads the specific file linked to (or the README.md) via JSDelivr's CDN.

Colección de páginas HTML5 con ejemplos y casos de uso del nuevo lenguaje de marcado así como de la combinación del mismo con estilos CSS de nivel 3, gráficos vectoriales SVG y script mediante ECMAScript 5.

Tool for turning many repos into a meta repo. why choose many repos or a monolithic repo, when you can have both with a meta repo? 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!

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. Rolls back the project to its previous state in case publishing fails. Pushes commits and tags (newly & previously created) to GitHub/GitLab. Enables two-factor authentication on new repositories. Opens a prefilled GitHub Releases draft after publish. See exactly what will be executed with preview mode, without pushing or publishing anything remotely.

phpEasyVCS is a simple version control system (VCS) with minimal hosting requirements, namely PHP 5.2+. No database is needed. Files can be viewed and uploaded with a browser or by WebDAV, which allows you to access the files like a local drive in all operating systems. For integration with other software a REST service is provided. It is very easy to view the file versions at a specific point in time. The web interface allows you to easily compare file versions and synchronize and merge local files with the files in phpEasyVCS. It is possible to host multiple repositories and define multiple users with full, read-only or no access to each of the repositories.

The Ascoos Build Number Display extension allows you to easily monitor the current build number of your workspace in the status bar of Visual Studio Code.

- Automatically updates @build and @updated tags in your PHP files. - Saves the build information in builds.json located in the .versions folder. - Creates a backup of the saved file in the .repos folder with the updated build number and date. - Allows setting an initial build number via configuration. - Automatically creates and updates .vscode/settings.json to exclude the .versions and .repos folders from the file explorer.