This isn't click bait. We really did this! We work in a very large Javascript monorepo at Microsoft we colloquially call 1JS. It's large not only in terms of GB, but also in terms of sheer volume of code and contributions. We recently crossed the 1,000 monthly active users mark, about 2,500 packages, and ~20million lines of code! The most recent clone I did of the repo clocked in at an astonishing
Aha! Develop is the agile tool that links strategy to delivery. Learn more Do we need a monorepo? When I first joined Aha!, I was surprised by how well-structured the engineering onboarding program was. I spent several weeks getting to know all the teams and learning the pieces of our system. What I didn't realize at the time was these onboarding conversations gave me more than basic technical kno
One of the things that I like to do in my projects, is to make the git history as linear as possible. Usually this means to rebase commits onto the main branch, but it can also mean to only allow merges in one direction, from feature branches into main, never the other way around. It kind of depends on the project. Today I'm taking this one step further, and I'm introducing a new concept: extremel
Sapling is a new Git-compatible source control client. Sapling emphasizes usability while also scaling to the largest repositories in the world. ReviewStack is a demonstration code review UI for GitHub pull requests that integrates with Sapling to make reviewing stacks of commits easy. You can get started using Sapling today. Source control is one of the most important tools for modern developers,
Conventional Commits A specification for adding human and machine readable meaning to commit messages Conventional Commits 1.0.0 Summary The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer
You can use git move as a drop-in 10x faster replacement for git rebase (see the demo). The basic syntax is How do I install it? The git move command is part of the git-branchless suite of tools. See the installation instructions. What does “rebase” mean? In Git, to “rebase” a commit means to apply a commit’s diff against its parent commit as a patch to another target commit. Essentially, it “move
bit is an experimental modernized git CLI built on top of git that provides happy defaults and other niceties: command and flag suggestions to help you navigate the plethora of options git provides you autocompletion for files and branch names when using bit add or bit checkout automatic fetch and branch fast-forwarding reducing the likelihood of merge conflicts suggestions work with git aliases n
提供敏捷、瀑布、任务协同等多种项目模板，降低上手配置难度 可通过甘特图、Kanban、 Scrum 等方式管理项目进度，全局掌控和风险控制一目了然 通过自动化设置，减少重复性操作，进一步释放人力至业务开发
Ever since I gave my first talk about esoteric programming languages, I wanted to create my own one. Well, some years later, at the Recurse Center, I wanted to learn how to build compilers with LLVM, so that seemed like a good opportunity to try that! Presenting: Programs written in legit are defined entirely by the graph of commits in a Git repository. The content of the repository is ignored. le
For a long time I didn't know that even writing commit message can have its own "best practices". When I got in touch with git for the first time, this part was described with words like "...and here you can write something short about what's going on in the commit". Bad commit messages Look at the commit messages below. If you want to merge them, you realy don't know, what you are adding / changi
Introduction Software projects are displayed by Gource as an animated tree with the root directory of the project at its centre. Directories appear as branches with files as leaves. Developers can be seen working on the tree at the times they contributed to the project. Gource includes built-in log generation support for Git, Mercurial, Bazaar and SVN. Gource can also parse logs produced by severa
git-bug is a bug tracker that: is fully embedded in git: you only need your git repository to have a bug tracker is distributed: use your normal git remote to collaborate, push and pull your bugs! works offline: in a plane or under the sea? Keep reading and writing bugs! prevents vendor lock-in: your usual service is down or went bad? You already have a full backup. is fast: listing bugs or openin
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
