Skip to content

Add lightweight contributing guidance #102

@dwilding

Description

@dwilding

Capturing Nicolas's suggestion from #99:

Would be nice to develop a QA template so that other reviewers know how to test the changes locally and make sure all other features work

I also think it would be great for us to decide and record things like the expected contribution flow. E.g., a recommended approach to branches, forks, and merging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    developmentAffects people developing/testing the Django codebase or charm

    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