Merge pull request #42 from Luzefiru/staging

ci: add a proper staging environment, release v1.1.0, #minor

.github/CONTRIBUTING.md

@@ -13,11 +13,22 @@ email, or any other method with the owners of this repository before making a ch
 
 We use a simplified version of [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
 
+- this also applies to PRs
+
+## Versioning Conventions
+
+We take inspiration from [Semantic Versioning 2.0.0](https://semver.org/).
+
 ## Pull Request Process
 
 1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
 2. Update the README.md with details of changes to the interface; this includes new environment variables, exposed ports, valid file locations and container parameters.
-3. You may merge the Pull Request once you have the sign-off of the maintainers, or if you do not have permission to do that, you may request a maintainer to merge it for you.
+3. Your Pull Request will be merged to the preview environment by the maintainers once it's approved after review.
+4. Your changes won't reflect on the main website until enough testers have confirmed the preview environment to be stable and usable and when the maintainers create a new release.
+
+- by default, any merge to the `main` branch is a patch
+- when the commit message has a `#minor` string, it will be a minor release
+- `#major` applies the same way
 
 ## Issue Report Process
 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -49,3 +49,8 @@ _Smartphone (please complete the following information):_
 ## Additional Context
 
 _Add any other context about the problem here._
+
+<!-- If you want to contribute to the codebase, uncomment the section below and feel free to fork the repo and make a PR to close this issue. -->
+
+<!-- ## Would I like to work on this? -->
+<!-- Yes. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -25,3 +25,8 @@ A clear and concise description of any alternative solutions or features you've
 
 _Additional context_
 Add any other context or screenshots about the feature request here.
+
+<!-- If you want to contribute to the codebase, uncomment the section below and feel free to fork the repo and make a PR to close this issue. -->
+
+<!-- ## Would I like to work on this? -->
+<!-- Yes. -->

.github/README.md

@@ -56,6 +56,10 @@ We'd love your help in improving the website with features, bug reports, and pat
 1. Read our [Contributing Guide](./CONTRIBUTING.md) before making an issue or pull request.
 2. [Fork this repository](https://github.com/Luzefiru/wuwatracker/fork) and start working on your own repository before making a pull request.
 
+#### Apply as a Tester
+
+If you're interested in testing new features, head over to our [Discord Server](https://discord.gg/mADnEXwZGT) and read the pinned messages in the `#tester-application` text channel.
+
 ### For Feature Requests or Bug Reports
 
 [Create an issue](https://github.com/Luzefiru/wuwatracker/issues/new/choose) while following the specific templates.

.github/workflows/tag.yml

@@ -0,0 +1,20 @@
+name: Tagging Pipeline
+
+on:
+  # on every push to main branch
+  push:
+    branches:
+      - main
+
+jobs:
+  tag_release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Bump version and push tag
+        if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' && contains(join(github.event.commits.*.message, ' '), '#skip') != true}}
+        uses: anothrNick/github-tag-action@a2c70ae13a881faf2b4953baaa9e49731997ab36
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          DEFAULT_BUMP: patch
+          WITH_V: true

src/app/page.tsx

@@ -16,7 +16,7 @@ export default function LandingPage() {
             role="alert"
           >
             <span className="text-xs bg-primary-600 rounded-full text-muted-foreground px-2.5 py-1.5">
-              v1.0.0
+              v1.1.0
             </span>
             <span className="text-sm">Wuwa Tracker</span>
             <svg