Skip to content

filter-branch / rebase imminent in the coming weeks #732

Open
@tony

Description

@tony

I am going to filter-branch outdated text files like manual/ from the code base: https://github.com/tmux-python/tmux-manuals. To get an idea: gh docs

Sometime over the coming weeks. Hopefully this will be a one time thing

I also may create new screenshots / optimized gifs and replace the old ones to save space.

In principle I don't like these at all - but if I do it at all, the less interruption to future committers

tmuxp:

 ❯ git count-objects -vH
count: 0
size: 0 bytes
in-pack: 12810
packs: 1
size-pack: 5.84 MiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

(which I admit, isn't that bad, but I really want the repo to be lean as possible)

libtmux:

❯ git count-objects -vH
count: 0
size: 0 bytes
in-pack: 2869
packs: 1
size-pack: 924.35 KiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

In the mean time I am going to try to curate some nice screenshot / video examples and optimize them well.

On option I may take to keep the repo lean is keeping the images / docs in a git branch, e.g. gh-pages

Old PRs

Secondly, at about the same time, old PRs are going to be closed. In those cases I will let the author know to create a fresh PR

In most of these cases the PRs seem abandoned and I've given multiple requests to pings, but I've also let those PRs go a long time without getting to them, they definitively can (and should) open a new PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions