Skip to content

GitHub-based development process #9

@littledan

Description

@littledan

It looks like the current source-maps specification is in a Google Doc. This makes it a bit difficult to follow normal GitHub-based development processes, such as making PRs to change the specification. Has this group considered moving the specification checked into a repository to enable this workflow? For example, Bikeshed could be used for the specification document itself.

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