| Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
It's useful to keep track of the repositories, the code reviews, issues,
etc. It's also easier to do code reviews that way (at least the initial
reading).
|
|
|
|
|
|
|
|
It looks like these packages were moved to a new one named `git-modes'.
|
|
|
|
I don't have to deal with magit anymore, so I can drop all the stuff
that removed the VC stuff.
|
|
Work's monorepo is extremely large which is causing performance issues
for magit. But there's magit features that I want to use when working on
personal projects.
Split the configuration between work/personal so that I can still use
what I want when working on my projects.
|
|
Let's use HTTPS instead of SSH for all my projects.
|
|
I'm going to deprecate the SSH endpoint for gitea, and use HTTPS instead
for accessing the repositories.
For this, I need to configure properly the credential part for the
different forges (github/gitea for now), and update the URL in the forge
configuration for emacs.
|
|
Use it with the forge package.
|
|
Don't use the current branch when building a link to sourcegraph, as we
might be on a feature branch that is not available on the remote.
|
|
Since the hostname from the git remote is appended to
'sourcegraph.twitter.biz', we can get rid of the mapping and just build
the URL using `format`. This simplifies even more the solution.
|
|
The mapping for git.twitter.biz was incorrect.
The package `git-link' has functions to take to format the URL for
sourcegraph, we don't need to maintain them on our end, which simplifies
a bit the code.
|
|
This article [1] shows how to use sourcegraph with the package
`git-link'. However, it requires to modify the configuration of the
repository to add a new remote named 'git-link'. This is inconvenient,
and this can be automated.
This change adds a function to automatically generate the remote URL
when the remote origin of a repo is set to twitter.biz.
We also add the configuration for our own gitea instance.
[1] https://sideshowcoder.com/2020/07/02/opening-sourcegraph-from-emacs/
|
|
This packages help interacting with various forges. We add a new entry
to the default list for our own gitea instance.
|
|
|
|
The module `magit-repos' can list the status of git repositories under a
given path.
Since all my repositories are under `~/workspace`, it's easy to use `M-x
magit-list-repositories` to get a buffer with all my repositories, and
their status (are they dirty, etc).
|
|
When working with 'source', magit is extremely slow (source is a huge
repository, so it's not surprising). We can improve significantly
performances by disabling a number of hooks when running git status.
|
|
|
|
We're moving from go/cs (twitter's own code search) to sourcegraph. I'm
adding git-link and the configuration to go from emacs to our
sourcegraph instance.
Doing `git-link` in a file will take me to the file in sg, and doing
`git-link-commit` on a commit in magit will take me to the commit in sg.
|
|
|
|
Opening a file in source is extremely slow, and I'm guessing it's
related to git/magit, since I don't see this elsewhere. As suggested in
https://magit.vc/manual/magit/Performance.html and
https://magit.vc/manual/magit/Per_002dRepository-Configuration.html, I'm
disabling git from VC's backend, and disable refreshing the magit buffer
for source.
|
|
or stuff that I don't know what they do.
|
|
|
|
|
|
With a bigger font, on a 13" laptop, I want magit to be full frame, I
don't want anything splitted.
Move a couple of other settings to the `:custom` section of
`use-package`.
|
|
|
|
This is actually an easier thing to maintain.
|