jsdrupal / admin_ui Goto Github PK

Set them up automatically with enough permissions to be able to assign themselves to an issue and manage labels

https://emotion.sh/docs/introduction

Top level styles can be found here: https://github.com/drupal/drupal/blob/8.8.x/core/themes/claro/css/src/base/elements.pcss.css

It would be nice as a contributor to not have to remember executing eslint/prettier locally or wait for the tests to pass on github.

Idea

1. Run prettier on commit
2. Run eslint and tests (unit tests) on push

This way you can not create a PR, unless you fix those problems.
You can always bypass this using --no-verify on commits and PRs

We should replace this with https://www.drupal.org/project/jsonapi_cross_bundles

How to use it?

When someone does composer require drupal/admin_ui on their site, it should bundle the JavaScript application and make it available

When we commit the build artifacts to the relevant branch on drupal.org, it would be nice to parse out the authors/co-authors since the last commit and add them in the following format:
Issue #12345 by author1, author2, author3: Issue title
This will ensure they get a credit on drupal.org

https://github.com/jsdrupal/admin_ui/blob/8.x-1.x/.github/workflows/sync-repo-push-branch.yml#L36

This will allow the module to be installed with `composer require drupal/admin_ui" to any Drupal site.

• Code pushed or deleted from branches should be mirrored to https://www.drupal.org/project/admin_ui
• Releases created on GitHub should have the tag pushed to drupal.org, and a new release created (or manual steps included in instructions if this isn't possible to do in an automated way)
• Documentation on how to create a release

Add back the tests and linters from the previous project

• prettier
• eslint
• tslint?
• phpcs