Theia - Source control Extension
Soundcheck 3rd party integration with SCM
Theia - Source control extras Extension
Parse repository URLs to extract, SCM platform, domain, user, and project information.
Get repository user and project information from package.json file contents.
Prettier configuration for SCM-Manager related projects
Base class for defining the behavior between screwdriver and source control management systems
The annotate-scm-slug backend module for the catalog plugin.
ESLint configuration for scm-manager and its plugins
Agnostic software release tool for managing versions on changelog (keep-a-changelog), multi-format files (JSON, Makefile, text, TOML, YAML), and also for tagging source code of a Git repo
[](https://github.com/treelab/treelab-forest/actions/workflows/npm-publish.yml) [](https://www.
Babel configuration for scm-manager and its plugins
<p align="center"> <a href="https://www.npmjs.com/package/git-scm-hooks" target="_blank" rel="noopener noreferrer"> <img src="https://api.iconify.design/pajamas:hook.svg?color=%23fd610d" alt="logo" width='100'/></a> </p>
Jest presets for SCM-Manager and its plugins
Github implementation for the scm-base class
TypeScript configuration
snyk library and cli utility
MST backend project-ийн core project
Fossil SCM delta compression
Typescript wrapper equivalent for pgmq-rs
A Pulumi package for managing resources on Strata Cloud Manager.. Based on terraform-provider-scm: version v0.2.1
🔥 An extremely fast and efficient LRU cache for JavaScript with high compatibility (including Browsers).
A generic plugin for routing builds to specified scm
Automatic release framework based on conventional commits and semantic versioning
""
Provides an SCM agnostic way to manage subprojects with a workflow similar to the scm:externals feature of subversion. It's particularly useful for rails projects that have some plugins managed by svn and some managed by git. For example, "ext install git://github.com/rails/rails.git" from within a rails application directory will realize that this belongs in the vendor/rails folder. It will also realize that this URL is a git repository and clone it into that folder. It will also add the vendor/rails folder to the ignore feature for the SCM of the main project. Let's say that the main project is being managed by subversion. In that case it adds "rails" to the svn:ignore property of the vendor folder. It also adds the URL to the .externals file so that when this project is checked out via "ext checkout" it knows where to fetch the subprojects. There are several other useful commands, such as init, touch_emptydirs, add_all, export, status. There's a tutorial at http://nopugs.com/ext-tutorial The reason I made this project is that I was frustrated by two things: 1. In my opinion, the workflow for svn:externals is far superior to git-submodule. 2. Even if git-submodule was as useful as svn:externals, I would still like a uniform way to fetch all of the subprojects regardless of the SCM used to manage the main project.
wf makes it very easy to define your own workflow and tools (SCM, ticket manager, ...)