asv
git-from-the-bottom-up
asv | git-from-the-bottom-up | |
---|---|---|
3 | 32 | |
840 | 808 | |
1.1% | - | |
9.1 | 0.0 | |
9 days ago | about 1 month ago | |
Python | ||
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
asv
-
git-appraise – Distributed Code Review for Git
> All these workflows are a derivation of the source in the repository and keeping them close together has a great aesthetic.
I agree. Version control is a great enabler, so using it to track "sources" other than just code can be useful. A couple of tools I like to use:
- Artemis, for tracking issues http://www.chriswarbo.net/blog/2017-06-14-artemis.html
- ASV, for tracking benchmark results https://github.com/airspeed-velocity/asv (I use this for non-Python projects via my asv-nix plugin http://www.chriswarbo.net/projects/nixos/asv_benchmarking.ht... )
-
Is GitHub Actions suitable for running benchmarks?
scikit-image, the project that commissioned this task, uses Airspeed Velocity, or asv, for their benchmark tests.
-
Memory benchmarking tools
Problem - The project currently uses Airspeed Velocity for tracking the memory changes. But I am having a lot of trouble setting this up and using this tool for monitoring memory consumption on a regular basis. Are you guys aware of some other open-source tools that I can use instead of this? I am stuck with this thing for some time now. I would appreciate any help.
git-from-the-bottom-up
- Git from the Bottom Up
-
How Head Works in Git
Here's a great walk through for how Git works from the bottom up: https://jwiegley.github.io/git-from-the-bottom-up/
It's short, easy to understand and you'll understand HEAD.
-
git-appraise – Distributed Code Review for Git
Very tangential:
Gerrit also stores some of its configs in a git repo. I was setting up a new instance, but couldn't get Admin permissions because the way my auth front-end didn't play well with the docker image's assumptions.
Gerrit already does a lot of its work via non-standard references. For example, you don't push to a branch, `refs/branches/foo`, you push to a separate `refs/for/foo` namespace that creates the review.
Similarly, Group config is stored in the All-Users git repo [1], but in references created after a UUID, in `refs/groups/UU/UUID`.
I ended up having a to exercise the plumbiest of plumbing commands [2] to create a new commit from scratch (from a tree, from the index, from blobs), to update the group ref to add myself to the Administrators group (this, of course, requires a local shell and permissions on the Gerrit host). It was a great way to exercise what I had learned in Git from the Bottom Up [3]
[1] https://gerrit-review.googlesource.com/Documentation/config-...
[2] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects
[3] https://jwiegley.github.io/git-from-the-bottom-up/
- Setting up Huginn on Heroku
-
Books for learning Git
I found Git from the Bottom Up helpful. It is very short as well. Then refer to the official book when you want more detail.
- Good git course and/or where to practice real life scenarios?
-
the first time i had to deal with a huge git rebase conflict
I recently came across "Git from the Bottom Up by John Wiegley" (thanks to Coding Blocks podcast), he has a chapter about rebasing: https://jwiegley.github.io/git-from-the-bottom-up/1-Repository/7-branching-and-the-power-of-rebase.html
-
Git-SIM: Visually simulate Git operations in your own repos with a single termi
You won't have to put your entire life on break in order to understand the fundamentals of git and why it works the way it works. Going through https://jwiegley.github.io/git-from-the-bottom-up/ and really understanding the material will take you a couple of hours at max, but will save you a lot of time in the future.
Wanting to understand things before using them is hardly elitism, not sure why you would think that.
Just like you probably don't want to fix bugs without understand the cause, it's hard to use a tool correctly unless you know how the tool works.
- What is the most efficient way of learning and comprehending Git?
What are some alternatives?
pyperformance - Python Performance Benchmark Suite
lisp-koans - Common Lisp Koans is a language learning exercise in the same vein as the ruby koans, python koans and others. It is a port of the prior koans with some modifications to highlight lisp-specific features. Structured as ordered groups of broken unit tests, the project guides the learner progressively through many Common Lisp language features.
pybench - Python benchmark tool inspired by Geekbench.
devdocs - API Documentation Browser
scikit-image - Image processing in Python
mark-sweep - A simple mark-sweep garbage collector in C
fashion-mnist - A MNIST-like fashion product database. Benchmark :point_down:
git-appraise - Distributed code review system for Git repos
pyeventbus - Python Eventbus
git-fire - :fire: Save Your Code in an Emergency
pytest-benchmark - py.test fixture for benchmarking code
emlop - EMerge LOg Parser