Skip to content

Issue and PR Criteria #1

@sudoforge

Description

@sudoforge

This issue hopes to provide clarity on what constitutes a valid issue or PR in this fork

This is a (hopefully temporary) fork. As such, I will be extremely selective about the type of contributions I will accept, and the types of issues I will support. It's a pretty short list.

Issues or PRs related to gopass integration on any platform

I would love for you to bring your bugs and bug fixes to me. I'll do what I can to fix them. I largely just copied the existing pass integration, so there's nothing novel about the gopass implementation. If you spot optimizations, feel free to submit those too.

Issues related to rebasing on top of upstream

I do not (yet) have automation for rebasing this repository on top of upstream. Doing so will be provided on a "best-effort" basis, with a goal of doing so weekly-ish. If I'm woefully behind, or you just need that latest commit, open an issue to ping me. I'll get around to it as soon as possible.

That said, upstream is not a very active/busy repository (at the time of writing, the most recent commit on HEAD is 2 months old); there is likely not going to be any conflict in this tree, because it is additive.


Please do not open an issue or pull request for any other reason. I do not have the capacity, nor desire, to support other features of this tool at this point in time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions