| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
