Project maintainers

Maintaining the UIkit project using git and

If you are a maintainer of the UIkit project, this topic goes over common tasks to help automate the process of comitting your changes back to the repository and creating release branches/tags. These topics are not helpful unless you are a maintainer, but feel free to continue reading to learn how the UIkit team has lessened the burden of extensive Drupal theme development.

Drupal 8 theme development is rewarding work that may seem overly repetitive at times. The goal of these topics is to make common tasks far more automated for you. Development tasks will be continuously improved over time, so your feedback is greatly appreciated.

If you have any questions or suggestions, feel free to create an issue in the UIkit issue queue.

The level of access you have to the UIkit project as a co-maintainer depends on the role assigned to you by the UIkit project lead.

Once you request a co-maintainer role through the UIkit issue queue, one or more of the following roles will be assigned to you:

  • Git maintainer: Allows a user to commit or push to the repository associated with this project.
  • Project co-maintainer: Allows a user to edit the project page and modify its settings, as well as co-maintain the documentation site at
  • Issue queue maintainer: Allows a user to assign issues to other issue maintainers for this project.
  • Release maintainer: Allows a user to create and update releases, and to control which branches are recommended or supported.

Another role (Administer maintainers) does exist, but will not be assigned to anyone other than the project lead.

Your initial roles will be assigned based on your level of expertise in one or more of the above roles. Additional roles can be assigned as your involvement in the project progresses.

Strict adherence to the Drupal Code of Conduct is to be expected, with those not in compliance being stripped of their project role(s) at the sole discretion of the project lead.

Log in