Skip to content

Please provide description and summary of a PR when we submit it #29

@chrishkchris

Description

@chrishkchris

When we submit a PR, please write the summary of the PR and provide the description.

Otherwise, it is difficult for other team members to known what have been done and its effect to our code.

This is an acceptable example of a PR with description
#27

It is also good to provide more details, especially for those PRs which affects the APIs and input output formats

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