Change Organization

.github/release-drafter.yml

@@ -4,6 +4,7 @@ categories:
   - title: '🔥 Breaking Changes'
     labels:
       - 'breaking'
+      - 'break'
   - title: '🚀 Features'
     labels:
       - 'feature'
@@ -37,6 +38,10 @@ template: |
   **Full Changelog**: https://github.com/$OWNER/$REPOSITORY/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION
 
 autolabeler:
+  - label: 'feature'
+    title:
+      - '/feature/i'
+      - '/feat/i'
   - label: 'documentation'
     files:
       - '*.md'
@@ -56,6 +61,3 @@ autolabeler:
   - label: 'deprecation'
     title:
       - '/deprecate/i'
-  - label: 'feature'
-    title:
-      - '/feature/i'

.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Scala CI
+on:
+  pull_request:
+  push:
+    branches: [ "master" ]
+jobs:
+  build:
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - os: ubuntu-latest
+            java: 8
+          - os: ubuntu-latest
+            java: 11
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-java@v4
+        with:
+          distribution: temurin
+          java-version: ${{ matrix.java }}
+
+      - uses: sbt/setup-sbt@v1
+
+      - name: Create header and run scalafmt
+        run: sbt headerCreateAll scalafmtAll
+
+      - name: Build and Test
+        run: sbt -v +test
+
+      # Optional: This step uploads information to the GitHub dependency graph and unblocking Dependabot alerts for the repository
+      #- name: Upload dependency graph
+      # uses: scalacenter/sbt-dependency-submission@ab086b50c947c9774b70f39fc7f6e20ca2706c91

.github/workflows/releases.yml

@@ -1,29 +1,24 @@
 name: Release
 on:
   push:
-    tags:
-      - v*
+    branches: [master, main]
+    tags: ["*"]
 jobs:
   publish:
     runs-on: ubuntu-latest
     steps:
-
-      - name: Checkout
-        uses: actions/checkout@v4
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-
-      - name: Set up JDK
-        uses: actions/setup-java@v4
+      - uses: actions/setup-java@v4
         with:
           distribution: temurin
-          java-version: 8
+          java-version: 11
           cache: sbt
-
-      - name: Release
-        run: sbt ci-release
+      - uses: sbt/setup-sbt@v1
+      - run: sbt ci-release
         env:
           PGP_PASSPHRASE: ${{ secrets.PGP_PASSPHRASE }}
           PGP_SECRET: ${{ secrets.PGP_SECRET }}
-          SONATYPE_USERNAME: ${{ secrets.SONATYPE_USERNAME }}
           SONATYPE_PASSWORD: ${{ secrets.SONATYPE_PASSWORD }}
+          SONATYPE_USERNAME: ${{ secrets.SONATYPE_USERNAME }}

.scalafmt.conf

@@ -21,4 +21,7 @@ docstrings.style = Asterisk
 rewrite {
   rules = [SortImports, RedundantBraces]
   redundantBraces.maxLines = 1
-}
+}
+
+docstrings.wrap = no
+importSelectors = singleLine

CODE_OF_CONDUCT.md

@@ -0,0 +1,14 @@
+# Code of Conduct
+
+Every member of our community has the right to have their identity respected. The Typelevel community is dedicated to providing a positive experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, neurodivergence, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status.
+
+Everyone is expected to follow the [Typelevel Code of Conduct] when discussing the project on the available communication channels.
+
+## Moderation
+
+If you have any questions, concerns, or moderation requests, please contact a member of the [Typelevel Code of Conduct Committee] or reach out to a project moderator:
+
+- [Rafael Fernandez](mailto:[email protected])
+
+[Typelevel Code of Conduct]: https://typelevel.org/code-of-conduct
+[Typelevel Code of Conduct Committee]: https://typelevel.org/code-of-conduct#contact

CONTRIBUTING.md

@@ -0,0 +1,66 @@
+# Contributing to Criteria4s
+
+Thank you for considering contributing to Criteria4s! We welcome contributions from the community to improve this project. Below are some guidelines to help you get started.
+
+## Code of Conduct
+
+Please adhere to our [Code of Conduct](CODE_OF_CONDUCT.md) during your interactions in the project repository. We strive to provide a welcoming and inclusive environment for all contributors.
+
+## How to Contribute
+
+### 1. Fork the Repository
+
+Fork the repository on GitHub by clicking the "Fork" button at the top right of the page.
+
+### 2. Clone Your Fork
+
+Clone your fork to your local machine:
+
+```sh
+git clone https://github.com/your-username/criteria4s.git
+cd criteria4s
+```
+
+### 3. Create a Branch
+
+Create a branch for your feature or bug fix:
+
+```sh
+git checkout -b my-feature-branch
+```
+
+### 4. Make Changes
+
+Make your changes to the code. Ensure your code adheres to the project's coding standards.
+
+### 5. Commit Your Changes
+
+Commit your changes with a descriptive commit message:
+
+```sh
+git commit -m "Add feature X"
+```
+
+### 6. Push to Your Fork
+
+Push your changes to your fork on GitHub:
+
+```sh
+git push origin my-feature-branch
+```
+
+### 7. Open a Pull Request
+
+Go to the original repository and open a pull request. Provide a clear and descriptive title and description of your changes.
+
+## Code of Conduct
+
+Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
+
+## Reporting Issues
+
+If you find a bug or have a feature request, please create an issue on GitHub. Provide as much detail as possible to help us address it.
+
+## Thank You!
+
+Thank you for contributing to Criteria4s! Your help is greatly appreciated.