-
-
-
----
-
-**Emoji is the 21st century's method of communication.** So no-one would be surprised that a modern enterprise company like Depth would want to follow, right?
-That should answer all your questions, except one - how do you go around using emoji on a website like GitHub (and still look professional π)?
-
-There are many ways in which you'd do this. That's what this article is about.
-
-### 1οΈβ£ Emoji in discussions
-
-The first way of using emoji is simple. Using emoji in discussions.
-Emoji in discussions can be used to convey anything. Difficult to explain something? There's an emoji. π‘ Not sure if the collaborator your speaking to speaks the same language? There's an emoji. π‘
-Emoji is very useful - you've got to give kudos to the Japanese for that one.
-
-Emoji in discussion is useful to convey concepts or show signs of affection β€οΈ, thanks π« or other cultural medium of appreciation π. It's away to simplify and modernise long texts;
-no need for that long-forgotten ***TL;DR*** at the start of every message.
-
-### 2οΈβ£ Emoji in reaction
-
-Emoji can be used to show your reaction - as subtle as you want it.
-They portray what we think of someone else's comment, and can be used to express approval or disapproval without needing to create another message and fill up the discussion.
-Reactions are also useful for community upvoting/downvoting, especially for big projects with lots of feature requests.
-GitHub lets us use the following emoji to react to other's messages: π, π, π, π, π, β€οΈ, π and π.
-
-**Unsure of what these emoji mean?**
-Here's a little definition of each for your convenience.
-
-- π Thumbs up: form of positive acknoledgment - Looks Good To Me, I agree!, Sure!, Okay, Let's give it a try, Upvote etc.
-- π Thumbs down: form of negative acknoledgment - Doesn't look right, I disagree.., Unsure, Not possible, Having second thoughts, Downvote etc.
-- π Smile: form of willingness, nostalgia, or other positive emotion - Thanks!, I agree!, Sure!, I'm fine with this! etc.
-- π Confetti: form of excitedness or success - It builds!, It works!, Let's get this started!,
-- π Confusion: form of disapproval or lack of understanding - Something's wrong, I don't understand, I don't agree, Unsure, I see faults etc.
-- β€οΈ Heart: form of thanks or appreciation - Thanks!, How kind!, That means so much to me!, You'd do that? etc.
-- π Rocket: form of experimentation, willingness or success - Let's get this started!, #InsiderBuild, Oops lol it crashed, It might not work but let's try, Go ahead! etc.
-- π Eyes: form of general acknoledgment - Okay, Sure, I don't mind, No worries, Got it etc.
-
-### 3οΈβ£ Emoji in commits
-
-Ever heard of [Gitmoji](https://gitmoji.dev)? Yep, that term really exists.
-It's a standard for including emoji inside your commits.
-
-At Depth, we encourage our team to use that standard as much as possible for two reasons: a) it makes the GitHub repo page look colourful π
-(but honestly, it makes such a change seeing all that lovely colour π¨ on the front-page rather than boring messages in grey font! π₯±) and b) sometimes, emoji in commits is
-just more descriptive than the commit messages themselves π€―! Writing commit messages is long and tedious, and it's always difficult to include the right wording, especially
-when making just a quick change, or so many changes you can't keep track of what you've been doing! π€¦
-
-Just putting a little emoji before your commit message really makes all the difference! π‘
-
-### 4οΈβ£ Emoji in code
-
-Ok, not literally. *~~please don't put random emoji in important pieces of code~~*
-
-**This sub-article is now called 4οΈβ£ Emoji in code comments** (π )
-
-Using emoji in code comments is exactly like using emoji in commits.
-It makes the code seem a) more casual and friendly and b) more descriptive! Sometimes even developers need a little bit of colour in their lives after hours
-of looking at the same boring file, fixing the same boring problem.. π΄ (and when I say colour I mean emoji. Looks like today's not your day, code highlighting π’)
-
-It can also be used to display guides and short bits of info, as well as titbits.
-
-### π Titbits
-
-Just a side-note, but I thought it was worth including in this article - but titbits are a great way of displaying information.
-
-Usually starting with the π emoji, titbits are an extra and perhaps irrelevant piece of information, or a tip.
-Titbits are useful in code comments, git commit descriptions, or wiki and README articles.
-
-As well as this, 'π' is also the Gitmoji for documentation!
From fa37c9665a6db64c22735745ee71a62e1516aa4e Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 20:55:47 +0700
Subject: [PATCH 03/10] Delete enterprise/EntraID.css
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
enterprise/EntraID.css | 218 -----------------------------------------
1 file changed, 218 deletions(-)
delete mode 100644 enterprise/EntraID.css
diff --git a/enterprise/EntraID.css b/enterprise/EntraID.css
deleted file mode 100644
index 4decf52..0000000
--- a/enterprise/EntraID.css
+++ /dev/null
@@ -1,218 +0,0 @@
-@import url('https://fonts.googleapis.com/css2?family=Segoe+UI:wght@400;600;700&display=swap');
-
-body {
- font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
- background-color: #f3f2f1;
- color: #323130;
- margin: 0;
- padding: 0;
-}
-
-a, a:link {
- color: #0078d4;
- text-decoration: none;
-}
-
-a:hover {
- color: #004578;
- text-decoration: underline;
-}
-
-a:focus {
- outline: 2px solid #0078d4;
- outline-offset: 2px;
-}
-
-a:active {
- color: #004578;
-}
-
-.ext-background-image {
- background-image: url('https://github.com/user-attachments/assets/8d475fbb-2075-4992-b7e8-37822f0ab4a9');
- background-size: cover;
- background-position: center;
-}
-
-.ext-header {
- background-color: #ffffff;
- padding: 16px;
- border-bottom: 1px solid #e1e1e1;
- display: flex;
- align-items: center;
- justify-content: space-between;
-}
-
-.ext-header-logo {
- height: 32px;
-}
-
-.ext-middle {
- display: flex;
- justify-content: center;
- align-items: center;
- min-height: 100vh;
- background-color: #f3f2f1;
- padding: 20px;
-}
-
-.ext-vertical-split-main-section {
- display: flex;
- height: 100vh;
-}
-
-.ext-vertical-split-background-image-container {
- flex: 1;
- background-image: url('https://github.com/user-attachments/assets/8d475fbb-2075-4992-b7e8-37822f0ab4a9');
- background-size: cover;
- background-position: center;
-}
-
-.ext-sign-in-box {
- background-color: #ffffff;
- padding: 24px;
- box-shadow: 0 1.6px 3.6px rgba(0, 0, 0, 0.132), 0 0.3px 0.9px rgba(0, 0, 0, 0.108);
- border-radius: 8px;
- width: 100%;
- max-width: 400px;
- text-align: center;
-}
-
-.ext-title {
- font-size: 24px;
- font-weight: 600;
- margin-bottom: 16px;
- color: #323130;
-}
-
-.ext-subtitle {
- font-size: 14px;
- color: #605e5c;
- margin-bottom: 24px;
-}
-
-.ext-input.ext-text-box {
- width: 100%;
- padding: 10px;
- margin-bottom: 16px;
- border: 1px solid #e1e1e1;
- border-radius: 8px;
- font-size: 14px;
- box-sizing: border-box;
-}
-
-.ext-input.ext-text-box.ext-has-error {
- border-color: #e81123;
-}
-
-.ext-input.ext-text-box:hover {
- border-color: #0078d4;
-}
-
-.ext-input.ext-text-box:focus {
- border-color: #0078d4;
- box-shadow: 0 0 0 1px #0078d4;
- outline: none;
-}
-
-.ext-input.ext-text-box:focus:hover {
- border-color: #005a9e;
- box-shadow: 0 0 0 1px #005a9e;
-}
-
-.ext-boilerplate-text {
- font-size: 12px;
- color: #605e5c;
- margin-top: 16px;
-}
-
-.ext-promoted-fed-cred-box {
- background-color: #f3f2f1;
- padding: 16px;
- border-radius: 8px;
- margin-top: 16px;
-}
-
-.ext-button.ext-primary {
- background-color: #0078d4;
- color: #ffffff;
- border: none;
- padding: 10px 20px;
- font-size: 14px;
- font-weight: 600;
- cursor: pointer;
- border-radius: 8px;
- margin-top: 20px;
- width: 100%;
-}
-
-.ext-button.ext-primary:hover {
- background-color: #005a9e;
-}
-
-.ext-button.ext-primary:focus {
- outline: 2px solid #005a9e;
- outline-offset: 2px;
-}
-
-.ext-button.ext-primary:active {
- background-color: #004578;
-}
-
-.ext-button.ext-secondary {
- background-color: #ffffff;
- color: #0078d4;
- border: 1px solid #0078d4;
- padding: 10px 20px;
- font-size: 14px;
- font-weight: 600;
- cursor: pointer;
- border-radius: 8px;
- margin-top: 20px;
- width: 100%;
-}
-
-.ext-button.ext-secondary:hover {
- background-color: #f3f2f1;
-}
-
-.ext-button.ext-secondary:focus {
- outline: 2px solid #005a9e;
- outline-offset: 2px;
-}
-
-.ext-button.ext-secondary:active {
- background-color: #e1e1e1;
-}
-
-.ext-error {
- color: #e81123;
- font-size: 12px;
- margin-top: 8px;
-}
-
-/*
-.ext-footer {
- background-color: #ffffff;
- padding: 16px;
- border-top: 1px solid #e1e1e1;
- text-align: center;
- font-size: 12px;
- color: #605e5c;
-}
-
-.ext-footer-links {
- display: flex;
- justify-content: center;
- margin-bottom: 8px;
-}
-
-.ext-footer-item {
- margin: 0 8px;
-}
-*/
-
-.ext-debug-item {
- margin-top: 8px;
- color: #605e5c;
- font-size: 12px;
-}
From 417a8a88a70da82436d60e2214f71346fda16cd7 Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 20:56:19 +0700
Subject: [PATCH 04/10] Delete template/ROOT.md
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
template/ROOT.md | 128 -----------------------------------------------
1 file changed, 128 deletions(-)
delete mode 100644 template/ROOT.md
diff --git a/template/ROOT.md b/template/ROOT.md
deleted file mode 100644
index a6ab0b0..0000000
--- a/template/ROOT.md
+++ /dev/null
@@ -1,128 +0,0 @@
-
-
-# πΌοΈ {repo name pretty}
-
-#### {repo description noemoji}
-
-
-
-### π¨ Building from source
-
-This is the best way to ensure you're on the most recent update in the code stream. However, this is experimental and certain functions may not work as intended.
-See [this section](#-building-the-code).
-
-### πΈ Screenshots
-
-{screenshot one}|{screenshot two}|{screenshot three}
----|---|---
-[](https://github.com/RiversideValley/Emerald)|[](https://github.com/RiversideValley/Emerald)|[](https://github.com/RiversideValley/Emerald)
-
-## π¦ Contributing & Feedback
-
-There are multiple ways to participate in the community:
-
-- Upvote popular feature requests
-- [Submit a new feature](https://github.com/RiversideValley/{repo name}/pulls)
-- [File bugs and feature requests](https://github.com/RiversideValley/{repo name}/issues/new/choose).
-- Review source [code changes](https://github.com/RiversideValley/{repo name}/commits)
-
-### ποΈ Codebase Structure
-
-
-
-```
-.
-βββEmerald.App // Emerald app code and packager
-| βββEmerald.App // Emerald app code (such as code related to UI but not Minecraft)
-| βββEmerald.App.Package // Package code for generating an uploadable MSIX bundle.
-βββEmerald.Core // Emerald core code (such as code related to launching and modifying Minecraft
-βββEmerald.CoreX // Emerald core code for the ability to run different Minecraft installation profiles and mods.
-```
-
-## π¨ Building the Code
-
-### 1οΈβ£ Prerequisites
-
-Ensure you have following components:
-
-
-
-- [Git](https://git-scm.com/)
-- [Visual Studio 2022](https://visualstudio.microsoft.com/vs/) with following individual components:
- - Universal Windows Platform Software Development Kit
- - .NET 7
- - Windows App Software Development Kit
- - Windows 11 SDK
-- [Windows 11 or Windows 10](https://www.microsoft.com/en-us/windows) (version 1809+)
-- At least 4GB of RAM
-- [Microsoft Edge WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/)
-
-### 2οΈβ£ Git
-
-Clone the repository:
-
-```git
-git clone https://github.com/RiversideValley/{repo name}
-```
-(`main` is the latest branch)
-
-### 3οΈβ£ Build the project
-
-- Open `Emerald.sln`.
-- Set the Startup Project to `Emerald.Package`
-- Build with `DEBUG|x64` (or `DEBUG|Any CPU`)
-
-## βοΈ License
-
-Copyright (c) {repo copyright} Riverside Valley Corporation
-
-Licensed under the MIT license as stated in the [LICENSE](LICENSE.md).
From b47ffcc18a125e19b00f59f64fa19bccb0e66d28 Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 20:56:38 +0700
Subject: [PATCH 05/10] Delete template directory
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
template/README.md | 3 ---
1 file changed, 3 deletions(-)
delete mode 100644 template/README.md
diff --git a/template/README.md b/template/README.md
deleted file mode 100644
index 758b1f2..0000000
--- a/template/README.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# π README templates
-
-README templates for Riverside Valley repositories!
From effcb8e20be4cecc9919752c20862c1c1721419a Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 20:57:12 +0700
Subject: [PATCH 06/10] Delete .github directory
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
.github/CODEOWNERS | 1 -
.github/CODE_OF_CONDUCT.md | 104 --------------------
.github/ISSUE_TEMPLATE/bug_report.yml | 106 ---------------------
.github/ISSUE_TEMPLATE/code_quality.yml | 61 ------------
.github/ISSUE_TEMPLATE/config.yml | 9 --
.github/ISSUE_TEMPLATE/feature_request.yml | 93 ------------------
.github/ISSUE_TEMPLATE/spec.yml | 72 --------------
.github/SECURITY.md | 61 ------------
.github/pull_request_template.md | 28 ------
9 files changed, 535 deletions(-)
delete mode 100644 .github/CODEOWNERS
delete mode 100644 .github/CODE_OF_CONDUCT.md
delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml
delete mode 100644 .github/ISSUE_TEMPLATE/code_quality.yml
delete mode 100644 .github/ISSUE_TEMPLATE/config.yml
delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml
delete mode 100644 .github/ISSUE_TEMPLATE/spec.yml
delete mode 100644 .github/SECURITY.md
delete mode 100644 .github/pull_request_template.md
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
deleted file mode 100644
index ba66238..0000000
--- a/.github/CODEOWNERS
+++ /dev/null
@@ -1 +0,0 @@
-* @Lamparter
diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md
deleted file mode 100644
index 37f38b6..0000000
--- a/.github/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,104 +0,0 @@
-# π _Metropolitan_ Code of Conduct
-
-> [!NOTE]
-> This document contains the Metropolitan Code of Conduct, a custom code of conduct made specifically for **Riverside Valley** repositories and projects, inspired by the Citizen Code of Conduct.
-
-## π« Purpose
-
-A primary goal of all Riverside Valley projects is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
-
-This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
-
-We invite all those who participate in Riverside Valley projects to help us create safe and positive experiences for everyone.
-
-## ποΈ Open `Source/Culture/Tech` Citizenship
-
-A supplemental goal of this Code of Conduct is to increase open `source/culture/tech` citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
-
-Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
-
-If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
-
-## π Expected Behavior
-
-The following behaviors are expected and requested of all community members:
-
-- [ ] π Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
-- [ ] π€ Exercise consideration and respect in your speech and actions.
-- [ ] π« Attempt collaboration before conflict.
-- [ ] π€¬ Refrain from demeaning, discriminatory, or harassing behavior and speech.
-- [ ] β Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
-- [ ] π§ Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
-
-## π€¬ Unacceptable Behavior
-
-The following behaviors are considered harassment and are unacceptable within our community:
-
-- [ ] π€¬ Violence, threats of violence or violent language directed against another person.
-- [ ] π«€ Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
-- [ ] π Posting or displaying sexually explicit or violent material.
-- [ ] πͺͺ Posting or threatening to post other people's personally identifying information ("doxing").
-- [ ] π Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
-- [ ] πΈ Inappropriate photography or recording.
-- [ ] ποΈ Inappropriate physical contact. You should have someone's consent before touching them.
-- [ ] π Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
-- [ ] π«£ Deliberate intimidation, stalking or following (online or in person).
-- [ ] π Advocating for, or encouraging, any of the above behavior.
-- [ ] βοΈ Sustained disruption of community events, including talks and presentations.
-
-## βοΈ Weapons Policy
-
-No weapons will be allowed at Riverside Valley events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.
-
-## βοΈ Consequences of Unacceptable Behavior
-
-Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
-
-Anyone asked to stop unacceptable behavior is expected to comply immediately.
-
-If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
-
-## π¬ Reporting Guidelines
-
-If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible via private Discord DM or by using one of the contact methods listed in the appropriate section.
-
-
-
-Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
-
-## π Addressing Grievances
-
-If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify Riverside Valley Corporation with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
-
-
-
-## πͺ Scope
-
-We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues--online and in-person--as well as in all one-on-one communications pertaining to community business.
-
-This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
-
-## πͺͺ Contact info
-
-You can contact us online via private Discord direct message. Unfortunately our Exchange365 Enterprise e-mail service is offline at this time making the afforementioned contact method the only solution.
-
-## βοΈ License and attribution
-
-> [!WARNING]
-> This code of conduct contains material inspired by the Citizen Code of Conduct. We do not recommend that this code of conduct is reused outside of a Riverside Valley project as it contains details specific to us.
-
-###### π§ββοΈ This code of conduct is distributed by Riverside Valley under the Creative Commons Attribution-ShareAlike license π€π
-
-_The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/)._
-
-_Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy)._
-
-```markdown
-Revision 2.3. Posted 6 March 2017.
-
-Revision 2.2. Posted 4 February 2016.
-
-Revision 2.1. Posted 23 June 2014.
-
-Revision 2.0, adopted by the Stumptown Syndicate (http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013.
-```
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
deleted file mode 100644
index 107603d..0000000
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ /dev/null
@@ -1,106 +0,0 @@
-name: Bug Report
-description: Create a bug report to help improve
-type: 'Bug'
-title: 'Bug: '
-body:
-
- # Tip to warn of checking for existing issues
- - type: markdown
- attributes:
- value: |
- > [!TIP]
- > Have you checked for similar issues? There's a possibility the bug you are experiencing has already been reported. Please do a thorough search before creating a new issue.
-
- # Description
- - type: textarea
- attributes:
- label: Description
- description: A clear and concise description of what the issue is.
- validations:
- required: true
-
- # Step to reproduce
- - type: textarea
- attributes:
- label: Steps to reproduce
- description: Steps to reproduce the behavior.
- placeholder: |
- 1.
- 2.
- 3.
- validations:
- required: true
-
- # Version
- - type: input
- id: app_version
- attributes:
- label: Version
- description: Which version are you using?
- placeholder: "e.g. 0.14.0-alpha3"
- validations:
- required: true
-
- # OS type
- - type: dropdown
- id: os
- attributes:
- label: Affected platforms
- description: |
- Select all or any platform that you see this issue on. This helps us determine if it's something platform-specific or in the core.
- multiple: true
- options:
- - π± Android
- - π² iOS
- - π» macOS
- - πͺ¨ Rosetta (macOS Catalyst)
- - πͺ Windows
- - πͺ WPF
- - π§ GTK
- - π§ Linux Framebuffer
- - β¨οΈ Skia Desktop
- - πΈοΈ WebAssembly
- - β Other
- - βΉοΈ I was unable to test on other platforms
-
- # OS Version
- - type: input
- id: os_version
- attributes:
- label: Platform version
- description: Which version of your OS are you using? Press Win + Pause/Break and copy or π (in menu bar) and About This Mac
- placeholder: "e.g. 10.0.22621.1848"
- validations:
- required: true
-
- # Note that the user should always upload the report rather than pasting it
- - type: markdown
- attributes:
- value: |
- > [!IMPORTANT]
- > Please **upload** the log file by clicking "Attach files".
- >
- > Feel free to remove sensitive information such as your usernames or drive names.
-
- # Log File
- - type: textarea
- attributes:
- label: Log File
- description: |
- Please upload the log file as an attachment
- placeholder: |
- Copy the log from the crash window or upload as an upload it from the log location.
- validations:
- required: true
-
- # Separator
- - type: markdown
- attributes:
- value: |
- ---
-
- # Additional Comments
- - type: textarea
- attributes:
- label: Comments
- description: Additional information, comments or screenshots about the issue.
diff --git a/.github/ISSUE_TEMPLATE/code_quality.yml b/.github/ISSUE_TEMPLATE/code_quality.yml
deleted file mode 100644
index 8958288..0000000
--- a/.github/ISSUE_TEMPLATE/code_quality.yml
+++ /dev/null
@@ -1,61 +0,0 @@
-name: Code Quality Issue
-description: Create a code quality issue to help keep a clean codebase
-title: 'Code Quality: '
-body:
-
- # Tip to warn of checking for existing issues
- - type: markdown
- attributes:
- value: |
- > [!TIP]
- > Have you checked for similar code quality issues? There's a possibility your suggestion is already being tracked. Please do a thorough search before creating a new issue.
-
- # Issue body
- - type: textarea
- attributes:
- label: Description
- description: A clear and concise description of what the code quality issue is.
- validations:
- required: true
-
- # Related code
- - type: textarea
- attributes:
- label: Concerned code
- description: A list of the different files and/or areas of the code concerned by the issue.
- validations:
- required: true
-
- # Gains
- - type: textarea
- attributes:
- label: Gains
- description: What would fixing this code quality issue bring to the source code?
- value: |
- - eg. A better readability.
- - eg. Uncoupling concepts X and Y.
- - eg. Clarifying the responsibility of class C.
- validations:
- required: true
-
- # Requirements
- - type: textarea
- attributes:
- label: Requirements
- description: Describe all the requirements to solve the code quality issue.
- value: |
- - eg. Using a specific design pattern.
- - eg. Separating Interface I into three new interfaces I1, I2 and I3.
- - eg. Regrouping the duplicated process into a new helper.
-
- # Separator
- - type: markdown
- attributes:
- value: |
- ---
-
- # Additional comments
- - type: textarea
- attributes:
- label: Comments
- description: Additional information, comments or screenshots about the code quality issue.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
deleted file mode 100644
index b52e140..0000000
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ /dev/null
@@ -1,9 +0,0 @@
-# It's recommended to override this file with other useful links like translation, forum, website, etc.
-blank_issues_enabled: false
-contact_links:
- - name: Question & Discussion
- url: https://dsc.gg/devsanx
- about: Post your questions and join the discussion. You can participate in chats on every channel.
-# - name: Support
-# url: mailto:support@theriversi.de
-# about: Errors relating to your account? Drop us an email!
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
deleted file mode 100644
index 8bf9522..0000000
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ /dev/null
@@ -1,93 +0,0 @@
-name: Feature Request
-description: This project thrives from differentiation from competing apps. Suggest an idea today!
-title: 'Feature: '
-body:
-
- # Tip to warn of checking for existing issues
- - type: markdown
- attributes:
- value: |
- > [!TIP]
- > Have you checked for similar feature requests? There's a possibility your suggestion is already being tracked. Please do a thorough search before creating a new issue.
-
- # Description
- - type: textarea
- attributes:
- label: What feature or improvement do you think would benefit the app?
- description: Please include your use case
- validations:
- required: true
-
- # Tooltip about requirements
- - type: markdown
- attributes:
- value: |
- Please include a list of changes required to make this improvement. A good rule of thumb is to start your proposal with no more than 7 high-level requirements.
-
- # Requirements
- - type: textarea
- attributes:
- label: Requirements
- description: Describe all the requirements to make your idea happen.
- value: |
- #### π High Priority
- - [ ] Something
- - [ ] Another thing
- - [ ] https://github.com/link/to/an/issue
-
- #### π Nice to have
- - [ ] Something
- - [ ] Another thing
- - [ ] https://github.com/link/to/an/issue
- validations:
- required: true
-
- # Version
- - type: input
- id: app_version
- attributes:
- label: Version
- description: Which version are you using?
- placeholder: "e.g. 0.14.0-alpha3"
-
- # Separator
- - type: markdown
- attributes:
- value: |
- ---
-
- - type: textarea
- id: api-changes
- attributes:
- label: API Changes
- description: Include a list of all API changes, additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code of usage of your new API.
- placeholder: |
- ```csharp
- var button = new Button ();
- button.MakeShiny = true; // new API
- ```
-
- The MakeShiny API works even if the button is already visible.
- validations:
- required: false
-
- - type: textarea
- id: use-case
- attributes:
- label: Intended Use-Case
- description: Provide a detailed example of where your proposal would be used and for what purpose. Focus on _why_ you want this feature instead of _what_ the feature does.
- placeholder: I have a situation where I would really want a shiny button to make it stand out from the rest of the plain and boring buttons.
- validations:
- required: false
-
- # Separator
- - type: markdown
- attributes:
- value: |
- ---
-
- # Additional comments
- - type: textarea
- attributes:
- label: Comments
- description: Additional information, comments or screenshots about the feature request.
diff --git a/.github/ISSUE_TEMPLATE/spec.yml b/.github/ISSUE_TEMPLATE/spec.yml
deleted file mode 100644
index a295cd3..0000000
--- a/.github/ISSUE_TEMPLATE/spec.yml
+++ /dev/null
@@ -1,72 +0,0 @@
-name: Spec
-description: An official specification for enhancements.
-assignees: []
-title: "Spec: "
-body:
- - type: markdown
- attributes:
- value: |
- Thank you for taking the time to provide us with a detailed specification of your idea.
-
- In a spec you will give a detailed and complete representation of the (public) APIs that are implemented as part of this change. Additionally please think about backwards compatibility, breaking changes, supported platforms and the difficulty.
- - type: textarea
- id: description
- attributes:
- label: Description
- description: Provide a concise description of the feature and the motivation for adding it. This can be a modified version from the feature request prior to this.
- validations:
- required: true
- - type: textarea
- id: api-changes
- attributes:
- label: API Changes
- description: Include a complete list of all API changes, additions, subtractions as would be required by your proposal.
- value: |
- ## `[ class ]`
-
- | API | Description |
- | ------------- | ------------- |
- | [name] | Gets or sets [description]. |
- validations:
- required: true
- - type: textarea
- id: usage-scenarios
- attributes:
- label: Usage scenarios
- description: Give us a couple of scenarios that demonstrate how developers would consume the above APIs.
- placeholder: |
- # C# Example
- ```csharp
- var thing = new MyNewControl();
- thing.BeAwesome = true;
- thing.Color = Colors.Cornsilk;
- ```
-
- # XAML Example
- ```xaml
-
- ```
- validations:
- required: true
- - type: textarea
- id: backwards-compatibility
- attributes:
- label: Backward Compatibility
- description: Please describe here anything in terms of backwards compatibility. Will there be breaking changes? Do we need to update dependencies to support this? What are the minimum supported API/OS levels? And lastly, are there any platforms that can't support this and why?
- placeholder: |
- Minimum API levels?
- Breaking changes?
- Unsupported platforms?
- validations:
- required: false
- - type: dropdown
- id: difficulty
- attributes:
- label: Difficulty
- description: What do you feel will be the difficulty of this change all things considering? No exact science, just your gut feeling.
- options:
- - Low
- - Medium
- - High
- validations:
- required: true
diff --git a/.github/SECURITY.md b/.github/SECURITY.md
deleted file mode 100644
index c1325d5..0000000
--- a/.github/SECURITY.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# π Security Policy
-
-#### This is our policy for reporting security vulnerabilities and overall guidelines on what you should do upon discovering one! π
-###### π This document also outlines the measures we have put in to prevent security vulnerabilities in the first place.
-
----
-
-
-
-## π Reporting Security Vulnerabilities
-
-
-
-#### Please use the GitHub Security Advisory "Report a Vulnerability" tab! π
-
-In order to report a security vulnerability, you can use GitHub's built-in tool which easily allows you to calculate an _attack vector/CVSS string_ or attribute to an existing [`CVE`](https://cve.org) code. This allows us to accurately calculate the severity and/or importance of preventing it.
-
-### π΅οΈ Spotting secrets in code
-
-If you spot a secret in the code, please let us know by contacting us. This helps us quietly remove the vulnerability without letting others abuse it.
-If you notice that we've accidentally published an app credential file or removed it from the `.gitignore` in the project root, please notify us.
-
-
-
-## βΉοΈ Our Measures
-##### What have we done to keep the app safe?
-
-### π€ Dependabot
-
-We have implemented Dependabot alerts to automatically track security vulnerabilities that apply to the repository's dependencies.
-
-### π Code scanning
-
-We have enabled GitHub Code Scanning to automatically scan our code for potential GitHub client secrets and other API tokens.
-
-### π‘οΈ Security advisories
-
-We have enabled GitHub security advisories to let us know if a potential security problem might affect our repository or if something doesn't look right with any of our other security vulnerability countermeasures. This makes it easy to track potential errors or problems that might expose user credentials publicly or cause other similar problems.
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
deleted file mode 100644
index 18ef16c..0000000
--- a/.github/pull_request_template.md
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-**Resolved / Related Issues**
-
-
-
-- Closes #
-
-**Steps used to test these changes**
-
-
-
-1. Opened the app...
-2. ...
-
----
-
-
From 59345d0697764de3627809377abe2adc079443af Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 20:57:26 +0700
Subject: [PATCH 07/10] Delete DISCLAIMER.md
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
DISCLAIMER.md | 167 --------------------------------------------------
1 file changed, 167 deletions(-)
delete mode 100644 DISCLAIMER.md
diff --git a/DISCLAIMER.md b/DISCLAIMER.md
deleted file mode 100644
index 568df88..0000000
--- a/DISCLAIMER.md
+++ /dev/null
@@ -1,167 +0,0 @@
-# π Global Disclaimer
-
-##### *Please note that many icons, fonts and other branding used for applications inside Riverside Valley are licensed to Riverside under certain licenses, and are as follows:*
-
-### π Microsoft Fluent Emoji
-
-
-
-Microsoft Fluent Emoji are used across multiple apps and services and are licensed to Riverside Valley under the following license:
-
-```
-
- MIT License
-
- Copyright (c) Microsoft Corporation.
-
- Permission is hereby granted, free of charge, to any person obtaining a copy
- of this software and associated documentation files (the "Software"), to deal
- in the Software without restriction, including without limitation the rights
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
- copies of the Software, and to permit persons to whom the Software is
- furnished to do so, subject to the following conditions:
-
- The above copyright notice and this permission notice shall be included in all
- copies or substantial portions of the Software.
-
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
- SOFTWARE
-
-```
-
-### π± Icons8
-
-
-
-Icons8 icons are used across multiple apps and services and are licensed to Riverside Valley under the following license:
-
-```
-
- Multiple icons provided by Icons8
-
-```
-
-
-
-### π ΎοΈ Ubuntu
-
-
-
-Ubuntu fonts are used across multiple apps and services and are licensed to Riverside Valley under the following license:
-
-```
-
- -------------------------------
- UBUNTU FONT LICENCE Version 1.0
- -------------------------------
-
- PREAMBLE
- This licence allows the licensed fonts to be used, studied, modified and
- redistributed freely. The fonts, including any derivative works, can be
- bundled, embedded, and redistributed provided the terms of this licence
- are met. The fonts and derivatives, however, cannot be released under
- any other licence. The requirement for fonts to remain under this
- licence does not require any document created using the fonts or their
- derivatives to be published under this licence, as long as the primary
- purpose of the document is not to be a vehicle for the distribution of
- the fonts.
-
- DEFINITIONS
- "Font Software" refers to the set of files released by the Copyright
- Holder(s) under this licence and clearly marked as such. This may
- include source files, build scripts and documentation.
-
- "Original Version" refers to the collection of Font Software components
- as received under this licence.
-
- "Modified Version" refers to any derivative made by adding to, deleting,
- or substituting -- in part or in whole -- any of the components of the
- Original Version, by changing formats or by porting the Font Software to
- a new environment.
-
- "Copyright Holder(s)" refers to all individuals and companies who have a
- copyright ownership of the Font Software.
-
- "Substantially Changed" refers to Modified Versions which can be easily
- identified as dissimilar to the Font Software by users of the Font
- Software comparing the Original Version with the Modified Version.
-
- To "Propagate" a work means to do anything with it that, without
- permission, would make you directly or secondarily liable for
- infringement under applicable copyright law, except executing it on a
- computer or modifying a private copy. Propagation includes copying,
- distribution (with or without modification and with or without charging
- a redistribution fee), making available to the public, and in some
- countries other activities as well.
-
- PERMISSION & CONDITIONS
- This licence does not grant any rights under trademark law and all such
- rights are reserved.
-
- Permission is hereby granted, free of charge, to any person obtaining a
- copy of the Font Software, to propagate the Font Software, subject to
- the below conditions:
-
- 1) Each copy of the Font Software must contain the above copyright
- notice and this licence. These can be included either as stand-alone
- text files, human-readable headers or in the appropriate machine-
- readable metadata fields within text or binary files as long as those
- fields can be easily viewed by the user.
-
- 2) The font name complies with the following:
- (a) The Original Version must retain its name, unmodified.
- (b) Modified Versions which are Substantially Changed must be renamed to
- avoid use of the name of the Original Version or similar names entirely.
- (c) Modified Versions which are not Substantially Changed must be
- renamed to both (i) retain the name of the Original Version and (ii) add
- additional naming elements to distinguish the Modified Version from the
- Original Version. The name of such Modified Versions must be the name of
- the Original Version, with "derivative X" where X represents the name of
- the new work, appended to that name.
-
- 3) The name(s) of the Copyright Holder(s) and any contributor to the
- Font Software shall not be used to promote, endorse or advertise any
- Modified Version, except (i) as required by this licence, (ii) to
- acknowledge the contribution(s) of the Copyright Holder(s) or (iii) with
- their explicit written permission.
-
- 4) The Font Software, modified or unmodified, in part or in whole, must
- be distributed entirely under this licence, and must not be distributed
- under any other licence. The requirement for fonts to remain under this
- licence does not affect any document created using the Font Software,
- except any version of the Font Software extracted from a document
- created using the Font Software may only be distributed under this
- licence.
-
- TERMINATION
- This licence becomes null and void if any of the above conditions are
- not met.
-
- DISCLAIMER
- THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
- EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF
- COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
- COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
- INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
- DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER
- DEALINGS IN THE FONT SOFTWARE.
-
-```
From 204ed196dc357008eb6b00b90b87e390dc0e3cfc Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 20:57:42 +0700
Subject: [PATCH 08/10] Delete profile/.README.md
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
profile/.README.md | 63 ----------------------------------------------
1 file changed, 63 deletions(-)
delete mode 100644 profile/.README.md
diff --git a/profile/.README.md b/profile/.README.md
deleted file mode 100644
index 4836266..0000000
--- a/profile/.README.md
+++ /dev/null
@@ -1,63 +0,0 @@
-#
-
-
-
-
-
-###### The future of computing starts now.
-
-#### We're [`Riverside Valley`](https://github.com/RiversideValley), an outstanding organisation owned by the Riverside Valley Corporation IT conglomerate that believes in people, not money.
-
-**π We're currently working on so many projects! Look out for Emerald, Flux, Protocol, Otherworld, and Inspire on your journey around our GitHub page!**
-
-**π« How to reach us: [`business@theriversi.de`](mailto:business@theriversi.de)** π Need help? [`support@theriversi.de`](mailto:support@theriversi.de)
-
-
-
From 77e01dab7565894c3a4923fff222439415c690e9 Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 21:00:32 +0700
Subject: [PATCH 09/10] Update README.md
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
profile/README.md | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/profile/README.md b/profile/README.md
index 5c0f3c8..bbd2121 100644
--- a/profile/README.md
+++ b/profile/README.md
@@ -1 +1,9 @@
-
+# Making Developer Sanctuary Great Again
+
+Join us on Discord https://discord.gg/5bkRHxV5MK
+
+Suggest Your Ideas!
+
+and vote Get
+
+
From f03916d397068b89866799d58ce6a336668dcb1b Mon Sep 17 00:00:00 2001
From: GetGet99 <41405393+GetGet99@users.noreply.github.com>
Date: Fri, 23 Jan 2026 21:00:47 +0700
Subject: [PATCH 10/10] Update README.md
Signed-off-by: GetGet99 <41405393+GetGet99@users.noreply.github.com>
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 336b106..6fefe93 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,3 @@
-# Devsanx
+# Devsanx .github
This is devsanx repository
-
-
-
-
-
-###### The future of computing starts now.
-
-#### We're [`Riverside Valley`](https://github.com/RiversideValley), an outstanding organisation owned by the Riverside Valley Corporation IT conglomerate that believes in people, not money.
-
-**π We're currently working on so many projects! Look out for Emerald, Flux, Protocol, Otherworld, and Inspire on your journey around our GitHub page!**
-
-**π« How to reach us: [`business@theriversi.de`](mailto:business@theriversi.de)** π Need help? [`support@theriversi.de`](mailto:support@theriversi.de)
-
-
- 
- 
- 
- 
- 
-