Skip to content

Use cases #13

@sethvincent

Description

@sethvincent

How might this be used?

As it is currently written, it requires that a user have a GitHub account. That's not a bad requirement for tech-related projects, but anything where we're expecting contributions from the general public we'll need a slightly different approach. Assume, though, that general public contributions are possible after implementing something like a bot that makes pull requests on people's behalf: #12

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions