mozsearch
ghstack
mozsearch | ghstack | |
---|---|---|
17 | 7 | |
234 | 554 | |
0.9% | - | |
8.9 | 8.5 | |
2 days ago | 16 days ago | |
Rust | Python | |
Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mozsearch
-
Firefox tooltip bug fixed after 22 years
- code browsing is primitive compared to https://searchfox.org/ (but most code browsing tool are, in comparison)
- my notifications are completely flooded by lots of useless information on GitHub, but that might be fixable
- our CI system (treeherder/taskcluster) scales, works on Linux/Mac/windows/Android and a bunch of version and arch, integrated with all of the other tools mentioned. Things such as auto-running tests based on the content of the patch, automatic categorization and prioritization of intermittent test failures, or auto-recording test failures and offering a pernosco recording showing the issue are just some of the features that we use daily without even thinking
-
Why SQLite Does Not Use Git
All the time. I would say at least 50% of my code browsing is done from my phone. I make heavily use of the mobile GitHub web interface for this (find-references support has been a godsend, search is still meh, I hate how they keep breaking basic find-in-page with SPA jank). Also Searchfox [0] when I need to comb through Firefox code (fast, excellent, no complaints).
Context: grad student, programming languages and systems research plus a bunch of IoT hacking on my own time. Either elder Gen Z or youngest possible Millennial, depending where you put the cutoff.
[0] https://searchfox.org
-
Sourcegraph is no longer Open Source
[4] is not really a usable 'product'. Livegrep (https://github.com/livegrep/livegrep) was inspired by it and is very usable.
[3] used to be a Google open source project as well, but it fell out of maintenance, and Sourcegraph took it over. It powers most of the basic regex/literal search in Sourcegraph.
Mozilla's code is searchable in Searchfox (https://searchfox.org/) which uses the indexer from Livegrep, combined with their own Git indexer and language-specific cross reference databases.
OpenGrok (https://github.com/oracle/opengrok) is also rather well known, but I have found it to have a slightly worse UI than alternatives.
-
Firefox 113.x quietly adds new Linux system requirements
Try using Searchfox to find references to those libraries. When you open a result, hover your mouse over the left column to see what commit added each line.
- Fetch API Implementation source
-
How to find the name of elements for firefox css
You might want to lokk at this, and this, and this .
- What environment variables does Firefox need on Linux?
-
Does this CSS rule crash anyone else's firefox?
Layout is hella broken, obviously, but it doesn't crash. You can do a search for progresschunck at https://searchfox.org to find what it means.
-
Swipe to navigate arrow indicator
https://searchfox.org/ should be you go-to tool to search Firefox code-base.
-
How to apply some css changes only to one (firefox's dark) theme?
Also, you can use browser toolbox to inspect Firefox UI and see what styles are being applied to it and to figure out what selectors to use. Of course, there is also https://searchfox.org/ for when you need to figure out exactly how Firefox is doing some feature x.
ghstack
- Reorient GitHub Pull Requests Around Changesets
-
Why SQLite Does Not Use Git
It seems like this is an idea that is really sticky.
[0] https://github.com/ezyang/ghstack
-
How much refactoring is too much for one PR?
And there are various tools to help make this workflow easier to manage. Graphite and ghstack, to name just two examples.
- Ghstack: Auto-Update Interdependent PRs
- Ghstack: Submit stacked diffs to GitHub on the command line
-
Stacked changes: how FB and Google engineers stay unblocked and ship faster
How is this different from ghstack? https://github.com/ezyang/ghstack (which is what Edward Yang for PyTorch developers to mimic the stacked workflow, although it works with other repos).
-
A Better Model for Stacked (GitHub) Pull Requests
While working on PyTorch, I also wrote an equivalent tool (funnily named nearly the same thing) for doing stack diffs (https://github.com/ezyang/ghstack/), which most of our team uses for more complicated PRs. The UX for working on commits is a bit different than this tool though; instead of pushing branches individually, you just run "ghstack" on a stack of commits and it will create a PR per commit in the chain (amending each commit so that its commit message records what PR it corresponds to). To update the PRs, just amend or interactive rebase the original commits. Personally, I find this a lot easier to handle than finagling tons of branches.
What are some alternatives?
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
git-stack - Stacked branch management for Git
hoogle - Haskell API search engine
graphite-cli - Graphite's CLI makes creating and submitting stacked changes easy.
sourcegraph - Code AI platform with Code Search & Cody
fossil-mirror - A test of the ability of the Fossil DVCS to mirror to GitHub
chrono - Date and time library for Rust
git-tools - Variaous tools for working with git.
codesearch - Fast, indexed regexp search over large file trees
git-ps - Patch Stack workflow CLI extension for Git
git-peek - git repo to local editor instantly
git-branchless - High-velocity, monorepo-scale workflow for Git