Open Source TypeScript Git Software

GitLens, part of GitKraken’s legendary Git tools, is an open-source extension for Visual Studio Code. GitLens supercharges Git inside VS Code and unlocks untapped knowledge within each repository. It helps you to visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more. GitLens simply helps you better understand code. Quickly glimpse into whom, why, and when a line or code block was changed. Jump back through history to gain further insights as to how and why the code evolved. Effortlessly explore the history and evolution of a codebase. Today, with over 18 million installs and over 120 million downloads, GitLens is loved and relied upon by millions of users, ranging from single developers to large enterprise teams.

Logseq is a privacy-first, open-source knowledge base that works on top of local plain-text Markdown and Org-mode files. Use it to write, organize and share your thoughts, keep your to-do list, and build your own digital garden. Logseq is a platform for knowledge management and collaboration. It focuses on privacy, longevity, and user control. The server will never store or analyze your private notes. Your data are plain text files and we currently support both Markdown and Emacs Org-mode (more to be added soon). In the unlikely event that the website is down or cannot be maintained, your data is, and will always be yours. No data lock-in, no proprietary formats, you can edit the same Markdown/Org-mode file with any tools at the same time. Connect your [[ideas]] and [[thoughts]] with Logseq. Your knowledge graph grows just as your brain generates and connects neurons from new knowledge and ideas.

View a Git Graph of your repository, and easily perform Git actions from the graph. Configurable to look the way you want! View annotated tag details (name, email, date and message) Copy commit hashes, and branch, stash & tag names to the clipboard. View commit details and file changes by clicking on a commit. View the Visual Studio Code Diff of any file change by clicking on it. Open the current version of any file that was affected in the commit. Copy the path of any file that was affected in the commit to the clipboard. Click on any HTTP/HTTPS url in the commit body to open it in your default web browser. Compare any two commits by clicking on a commit, and then CTRL/CMD clicking on another commit. View the Visual Studio Code Diff of any file change between the selected commits by clicking on it. Open the current version of any file that was affected between the selected commits.

BatNoter is a web application that allows users to store notes in their git repository. This is a frontend project built using mainly react (typescript), redux-toolkit & mui components. BatNoter API is the backend implementation of REST APIs which are used by this react app. Login with GitHub. Create, edit, delete, organize & explore notes easily with a nice & clean user interface. Markdown format supported allowing users to add hyperlink, table, headings, code blocks, blockquote... etc inside notes. Editor allows preview of markdown. Quickly copy code from the code section using copy to clipboard button. Store notes directly at the root or use folders to organize them (nesting supported). Explore all the notes from a specific directory with single click. All the notes are stored inside user's github repository. Notes are cached to avoid additional API calls. URLs can be bookmarked. Dark/Light mode supported.

Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like. You can include the action in your workflow to trigger any event that GitHub actions supports. If the remote branch that you wish to deploy to doesn't already exist the action will create it for you. Your workflow will also need to include the actions/checkout step before this workflow runs in order for the deployment to work. If you intend to make multiple deployments in quick succession you may need to leverage the concurrency parameter in your workflow to prevent overlaps. The with portion of the workflow must be configured before the action will work. You can add these in the with section found in the examples above. Any secrets must be referenced using the bracket syntax and stored in the GitHub repository's Settings/Secrets menu.

A JavaScript library to draw pretty git graphs. GitGraph.js codebase is a monorepo. Packages are released under @gitgraph/ scope. As a contributor, you might be interested in checking out gitgraph-core. It contains the core logic for rendering libraries to use. To help you get your feet wet and get you familiar with our contribution process, we have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place to get started. To draw git graphs examples that are easy to maintain

Introducing true design version control without changing your tools. Manage changes, document work and keep your team in sync. Enjoy all the benefits of git with our simple UI, leaving you more time to focus on what matters — your design. Create branches, collaborate with other designers or developers, and commit changes without touching the command line. Every pixel is completely open source. Build the features you need and become a part of future Kactus releases. It brings the entire git flow to sketch: branches, pull requests, team collaboration (you can work on the same file and automatically merge the changes), etc. You can share pages across multiple sketch files. You can publish pages on the internet and import them in another project (soon)!

An image bed management tool with CDN acceleration function developed based on GitHub API. No need to download and install, use it online on the web page! free! Stablize! Convenient! Extremely fast! Writing articles with static blogs such as Hexo, VuePress, Hugo, etc., I don’t know where to save the pictures. Deliberately spending money to rent a cloud server to host pictures, it is too expensive and not worth it, and the upload configuration is cumbersome. The link to the favorite picture copied from the Internet will become invalid one day after using it. Using other paid image beds, the speed is slow, the capacity is small, and the time and flow are limited. Looking for a picture bed that is really free, stable, unlimited in capacity, and fast in access speed. So, come and try the PicX picture bed , it is specially made for technical bloggers, whoever uses it will know. Support one- click copying of external links of pictures and one- click conversion of Markdown format.

This action makes it easy to quickly write a script in your workflow that uses the GitHub API and the workflow run context. To use this action, provide an input named script that contains the body of an asynchronous function call. Since the script is just a function body, these values will already be defined, so you don't have to import them. All scripts are now run with Node 16 instead of Node 12 and are affected by any breaking changes between Node 12 and 16. By default, the JSON-encoded return value of the function is set as the "result" in the output of a github-script step. For some workflows, string encoding is preferred. This option can be set using the result-encoding input. By default, requests made with the github instance will not be retried. You can configure this with the retries option.

commitlint checks if your commit messages meet the conventional commit format. commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. We identify ease of adoption and developer experience as fields where there is room and need for improvement. The items on the roadmap should enhance commitlint regarding those aspects.

Each diff provides a comprehensive visualization of the code changes, helping developers identify problems and better understand the changes. Each diff features a line-by-line and side-by-side preview of your changes. All the code changes are syntax highlighted using highlight.js, providing more readability. Similar lines are paired, allowing for easier change tracking. We work hard to make sure you can have your diffs in a simple and flexible way. The AI community building the future. Build, train and deploy state of the art models powered by the reference open source in natural language processing. Wrapper and helper adding syntax highlight, synchronized scroll, and other nice features. You can use it without syntax highlight or by passing your own implementation with the languages you prefer. Diff2Html can be used in various ways as listed in the distributions section.

Communicate important updates to your team via git commit messages. Sometimes you need to communicate changes to other developers on your project. In a small team, a Slack message works okay, but in larger teams and distributed organizations (such as open-source projects), reaching everyone can be a pain. git-notify allows you to embed announcements into your git commit messages. And display them to another developer on a machine, far far away. Just add "git-notify:" to your git commit message, and anything that follows will be displayed when another developer pulls that commit, or switches from a branch that does not contain that commit to one that does. If you're using a merge or squash commit strategy on GitHub, you can also add them to the extended commit message when landing a PR. git-notify will display a message for every "git-notify:" prefix it finds in the commit log that was just pulled/merged/rebased/checked out.

A JupyterLab extension for version control using Git. To see the extension in action, open the example notebook included in the Binder demo. Open the Git extension from the Git tab on the left panel. This extension tries to handle credentials for HTTP(S) connections (if you don't have set up a credential manager). But not for other SSH connections. The extension can cache temporarily (by default for an hour) credentials. To use the caching, you will need to check the option Save my login temporarily in the dialog asking your credentials. Once installed, extension behavior can be modified via the following settings which can be set in JupyterLab's advanced settings editor. Set post git init actions. It is possible to provide a list of commands to be executed in a folder after it is initialized as Git repository. Set path patterns to exclude from this extension. You can use wildcard and interrogation mark for respectively everything or any single character in the pattern.