Skip to content

project: add suitable workflows for pr, issue and code #59

@salihdev0

Description

@salihdev0

I think we should do the following to develop the project in a more standard way.

  • We should develop on development branch
  • eslint should be controlled not only with pre-commit but also with ci workflow. In some cases, pre-commit can be skipped.
  • we should write test
  • we need to add a workflow stage that controls the tests

Open to other ideas.

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