OpenWF/SpaceNinjaServer
28
29
Fork 34
Code Issues 25 Pull Requests 2 Actions Packages Projects Releases Activity

feat: add update and start script for dummies #828

Merged
Sainan merged 4 commits from 4dummies into main 2025-01-20 03:22:34 -08:00
Conversation 2 Commits 4 Files Changed 1 +22
Sainan commented 2025-01-19 08:28:38 -08:00
Owner
Copy Link
No description provided.
coderabbitai[bot] commented 2025-01-19 08:28:44 -08:00 (Migrated from github.com)
Author
Owner
Copy Link

Warning

Rate limit exceeded

@Sainan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 0597ddbb34 and e6dd10ba4f.

📒 Files selected for processing (1)
  • UPDATE AND START SERVER.bat (1 hunks)

Walkthrough

The pull request modifies the "UPDATE AND START SERVER.bat" batch script to automate a server update and startup process. The script performs a sequence of operations including pulling the latest changes from a Git repository, checking for the existence of a specific subdirectory (static\data\0\), updating that subdirectory if it exists, installing necessary Node.js packages, building the application, and starting the server. The batch file consolidates multiple command-line operations into a single executable script, streamlining the deployment workflow. No alterations to the declarations of exported or public entities were made in this diff.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.
<!-- This is an auto-generated comment: summarize by coderabbit.ai --> <!-- This is an auto-generated comment: rate limited by coderabbit.ai --> > [!WARNING] > ## Rate limit exceeded > > @Sainan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait **7 minutes and 45 seconds** before requesting another review. > > <details> > <summary>⌛ How to resolve this issue?</summary> > > After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. > > We recommend that you space out your commits to avoid hitting the rate limit. > > </details> > > > <details> > <summary>🚦 How do rate limits work?</summary> > > CodeRabbit enforces hourly rate limits for each developer per organization. > > Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. > > Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information. > > </details> > > <details> > <summary>📥 Commits</summary> > > Reviewing files that changed from the base of the PR and between 0597ddbb3416c7a0ae47c3c0c767a6d547d8ae34 and e6dd10ba4f2cea934d26621d34b25bdc183b4215. > > </details> > > <details> > <summary>📒 Files selected for processing (1)</summary> > > * `UPDATE AND START SERVER.bat` (1 hunks) > > </details> <!-- end of auto-generated comment: rate limited by coderabbit.ai --> <!-- walkthrough_start --> ## Walkthrough The pull request modifies the "UPDATE AND START SERVER.bat" batch script to automate a server update and startup process. The script performs a sequence of operations including pulling the latest changes from a Git repository, checking for the existence of a specific subdirectory (`static\data\0\`), updating that subdirectory if it exists, installing necessary Node.js packages, building the application, and starting the server. The batch file consolidates multiple command-line operations into a single executable script, streamlining the deployment workflow. No alterations to the declarations of exported or public entities were made in this diff. <!-- walkthrough_end --> <!-- internal state start --> <!-- FAHghAtBAEAqAWBLAztF0CGA7TBXALgPYQDmAplmQE4b5kAm0AxoQLasX4Bc0ADldEIAjAFZkm+RADcyqIQE9mhetQxChifADoMiaFAB8wY+CjHYmgDZkeAMzK0eGeo1y96tMpiyNk+DFT40MhMVIi8QbaEAvS47IiywABycULUPAAcAEwZwACqyOnQAMq6WNjGhiaQMBSMhLZ4RKQUqnSMLOycPPyCouKSMnKKLCo06po6elWmMAjo6NhNxOSUNO1KXVjc0DQA7sFxrAGKCkpjahrauvoQRtVm+QAKACIAgrAAotBvSS8lsDeACVYCVPkCAGrgrRCRzAABEiOAAGJkT8AJItNaeXxHE6CRpMeDYcjIczwLz8QhSRAqRj0RC2RqIbZUZS4JiyTDBagJVANTbHHyoIjc2H4InQWyIaxobZ1BhS6LQNweSRYEjeXz+QIszUYHlUGRULRwCnMYkarkspiWXAqbmdIWMUW8XCWSzQfDmyyePwWklc2xs1jcgDiml2ZF4hGQmmiilwcY10AABiRI26PanTQAxQgewh7PVepDIAA0pa8ITCEQt4gA1qgogJvV4yAAPFB0LCcgnc5C8cSMxBMaAMqgDBPQAAUqb8tFHAB01RglwAGJepgCUpvRjW96AnU6oik73YrVeCoXCQXKNJIfrlosj2EYQ6oLdYqGwhDbAnTTN3UsVMvUIFV3E8UtaEOIRjwkBNTTeWw6AESd8FwKgsBLUU20EMIM3KT14KIU9Kzwmtb2YDAPVQVMsF4UNEFAl8sAXD1oEoTlkGQfEkmUMgtBEVBeAwJgGwwUlK07cQCC5ejGN2XAcCEXAZXoFjwM6XgZS8PCMF4XhLFHRdCCwSs3ylFkaMsRQqGUuiGNDeycAXQJNOgX1lMlCjqGNLRjFRH5LFQ0y2LAq8VFtAIwv5RpOxjQJFWVN0hGMsdOE0PlKmgfjMBCtpEDMkVwLwqLfXWIrwoFBLog2FLcDS0doEyyQuT2agvGOB0WVLI9GVsALEXhSo7geWofH7DACBWVp1kVJ1ul2DADmQPFT2gM5RlUCZrmmMbZkFTQAH1aWQY7JxpMgOvoY63KCKpQBqTAhFsDAABZ13XeghCyd6AE56He96AGYADYwfXWwAHZ6AAVgARlsJhbHXf6yCEd76Fsf73rIMHoYR24jEO9c4f+2GfqEEH3oRsGmGhjB1wwMh3uhpgQaYdcGYJjAwfhtn6AyFmaeJ8ajvwU76HOy6Ehu466mJoA= --> <!-- internal state end --> <!-- tips_start --> --- Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? <details> <summary>❤️ Share</summary> - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code) </details> <details> <summary>🪧 Tips</summary> ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit <commit_id>, please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai generate docstrings` to [generate docstrings](https://docs.coderabbit.ai/finishing-touches/docstrings) for this PR. ([Beta](https://docs.coderabbit.ai/early-access#beta)) - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements. </details> <!-- tips_end -->
coderabbitai[bot] (Migrated from github.com) reviewed 2025-01-19 08:30:24 -08:00
coderabbitai[bot] (Migrated from github.com) left a comment
Author
Owner
Copy Link

Actionable comments posted: 4

🧹 Nitpick comments (2)
UPDATE AND START SERVER.bat (2)

1-9: Add script header and initialization checks.

The script should include a header with usage instructions and perform initialization checks.

Add this at the beginning of the script:

@echo off
setlocal enabledelayedexpansion

echo ===================================
echo Server Update and Startup Script
echo ===================================

:: Check if Git is installed
where git >nul 2>nul || (
    echo Git is not installed or not in PATH
    pause
    exit /b 1
)

:: Check if Node.js is installed
where node >nul 2>nul || (
    echo Node.js is not installed or not in PATH
    pause
    exit /b 1
)

:: Ensure we're in the correct directory
if not exist package.json (
    echo Please run this script from the project root directory
    pause
    exit /b 1
)

1-9: Consider adding a cleanup routine.

The script should handle cleanup of old builds and provide a way to terminate the server gracefully.

Consider adding these features:

  1. Clean old builds before updating
  2. Handle CTRL+C gracefully
  3. Backup configuration files
  4. Add a verbose mode for debugging
  5. Log operations to a file

Would you like me to provide an implementation for any of these features?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b19fda66a2 and abfa400db2.

📒 Files selected for processing (1)
  • UPDATE AND START SERVER.bat (1 hunks)
**Actionable comments posted: 4** <details> <summary>🧹 Nitpick comments (2)</summary><blockquote> <details> <summary>UPDATE AND START SERVER.bat (2)</summary><blockquote> `1-9`: **Add script header and initialization checks.** The script should include a header with usage instructions and perform initialization checks. Add this at the beginning of the script: ```batch @echo off setlocal enabledelayedexpansion echo =================================== echo Server Update and Startup Script echo =================================== :: Check if Git is installed where git >nul 2>nul || ( echo Git is not installed or not in PATH pause exit /b 1 ) :: Check if Node.js is installed where node >nul 2>nul || ( echo Node.js is not installed or not in PATH pause exit /b 1 ) :: Ensure we're in the correct directory if not exist package.json ( echo Please run this script from the project root directory pause exit /b 1 ) ``` --- `1-9`: **Consider adding a cleanup routine.** The script should handle cleanup of old builds and provide a way to terminate the server gracefully. Consider adding these features: 1. Clean old builds before updating 2. Handle CTRL+C gracefully 3. Backup configuration files 4. Add a verbose mode for debugging 5. Log operations to a file Would you like me to provide an implementation for any of these features? </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: .coderabbit.yaml** **Review profile: CHILL** **Plan: Pro** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between b19fda66a2ede1ff1450f869d642da3f78f0648c and abfa400db249d443660f7d51fcf09eb4df94e671. </details> <details> <summary>📒 Files selected for processing (1)</summary> * `UPDATE AND START SERVER.bat` (1 hunks) </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
UPDATE AND START SERVER.bat
coderabbitai[bot] (Migrated from github.com) commented 2025-01-19 08:30:23 -08:00
Author
Owner
Copy Link

🛠️ Refactor suggestion

Ensure consistent use of call and add error handling for npm operations.

The npm commands should be consistent in using call and include error handling.

-call npm i
+@echo Installing dependencies...
+call npm i || (
+    echo Failed to install dependencies
+    pause
+    exit /b 1
+)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

@echo Installing dependencies...
call npm i || (
    echo Failed to install dependencies
    pause
    exit /b 1
)
_:hammer_and_wrench: Refactor suggestion_ **Ensure consistent use of `call` and add error handling for npm operations.** The `npm` commands should be consistent in using `call` and include error handling. ```diff -call npm i +@echo Installing dependencies... +call npm i || ( + echo Failed to install dependencies + pause + exit /b 1 +) ``` <!-- suggestion_start --> <details> <summary>📝 Committable suggestion</summary> > ‼️ **IMPORTANT** > Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements. `````suggestion @echo Installing dependencies... call npm i || ( echo Failed to install dependencies pause exit /b 1 ) ````` </details> <!-- suggestion_end --> <!-- This is an auto-generated comment by CodeRabbit -->
coderabbitai[bot] (Migrated from github.com) commented 2025-01-19 08:30:23 -08:00
Author
Owner
Copy Link

🛠️ Refactor suggestion

Improve directory handling and add validation.

The script uses hard-coded paths and lacks directory validation.

-if exist static\data\0\ (
-	cd static\data\0\
-	git pull
-	cd ..\..\..\
-)
+if exist static\data\0\ (
+    @echo Updating data repository...
+    pushd static\data\0\ || (
+        echo Failed to enter data directory
+        pause
+        exit /b 1
+    )
+    git pull origin main || (
+        echo Failed to update data repository
+        popd
+        pause
+        exit /b 1
+    )
+    popd
+)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

if exist static\data\0\ (
    @echo Updating data repository...
    pushd static\data\0\ || (
        echo Failed to enter data directory
        pause
        exit /b 1
    )
    git pull origin main || (
        echo Failed to update data repository
        popd
        pause
        exit /b 1
    )
    popd
)
_:hammer_and_wrench: Refactor suggestion_ **Improve directory handling and add validation.** The script uses hard-coded paths and lacks directory validation. ```diff -if exist static\data\0\ ( - cd static\data\0\ - git pull - cd ..\..\..\ -) +if exist static\data\0\ ( + @echo Updating data repository... + pushd static\data\0\ || ( + echo Failed to enter data directory + pause + exit /b 1 + ) + git pull origin main || ( + echo Failed to update data repository + popd + pause + exit /b 1 + ) + popd +) ``` <!-- suggestion_start --> <details> <summary>📝 Committable suggestion</summary> > ‼️ **IMPORTANT** > Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements. `````suggestion if exist static\data\0\ ( @echo Updating data repository... pushd static\data\0\ || ( echo Failed to enter data directory pause exit /b 1 ) git pull origin main || ( echo Failed to update data repository popd pause exit /b 1 ) popd ) ````` </details> <!-- suggestion_end --> <!-- This is an auto-generated comment by CodeRabbit -->
UPDATE AND START SERVER.bat
@ -0,0 +1,22 @@
@echo off
echo Updating SpaceNinjaServer...
git pull
coderabbitai[bot] (Migrated from github.com) commented 2025-01-19 08:30:23 -08:00
Author
Owner
Copy Link

🛠️ Refactor suggestion

Add error handling and branch specification for git operations.

The git pull command should include error handling and specify the branch to avoid unintended merges.

-git pull
+@echo Updating repository...
+git pull origin main || (
+    echo Failed to update repository
+    pause
+    exit /b 1
+)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

@echo Updating repository...
git pull origin main || (
    echo Failed to update repository
    pause
    exit /b 1
)
_:hammer_and_wrench: Refactor suggestion_ **Add error handling and branch specification for git operations.** The `git pull` command should include error handling and specify the branch to avoid unintended merges. ```diff -git pull +@echo Updating repository... +git pull origin main || ( + echo Failed to update repository + pause + exit /b 1 +) ``` <!-- suggestion_start --> <details> <summary>📝 Committable suggestion</summary> > ‼️ **IMPORTANT** > Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements. `````suggestion @echo Updating repository... git pull origin main || ( echo Failed to update repository pause exit /b 1 ) ````` </details> <!-- suggestion_end --> <!-- This is an auto-generated comment by CodeRabbit -->
UPDATE AND START SERVER.bat
@ -0,0 +14,4 @@
call npm i
call npm run build
call npm run start
coderabbitai[bot] (Migrated from github.com) commented 2025-01-19 08:30:23 -08:00
Author
Owner
Copy Link

🛠️ Refactor suggestion

Add build validation and process management.

The build and start commands need error handling and process management.

-call npm run build
-call npm run start
+@echo Building application...
+call npm run build || (
+    echo Build failed
+    pause
+    exit /b 1
+)
+
+@echo Starting server...
+call npm run start || (
+    echo Server failed to start
+    pause
+    exit /b 1
+)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

@echo Building application...
call npm run build || (
    echo Build failed
    pause
    exit /b 1
)

@echo Starting server...
call npm run start || (
    echo Server failed to start
    pause
    exit /b 1
)
_:hammer_and_wrench: Refactor suggestion_ **Add build validation and process management.** The build and start commands need error handling and process management. ```diff -call npm run build -call npm run start +@echo Building application... +call npm run build || ( + echo Build failed + pause + exit /b 1 +) + +@echo Starting server... +call npm run start || ( + echo Server failed to start + pause + exit /b 1 +) ``` <!-- suggestion_start --> <details> <summary>📝 Committable suggestion</summary> > ‼️ **IMPORTANT** > Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements. `````suggestion @echo Building application... call npm run build || ( echo Build failed pause exit /b 1 ) @echo Starting server... call npm run start || ( echo Server failed to start pause exit /b 1 ) ````` </details> <!-- suggestion_end --> <!-- This is an auto-generated comment by CodeRabbit -->
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
An existing implemention is incorrect
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
enhancement
New feature or request specific to the emulator
help wanted
Extra attention is needed
improvement
missing data
part of more major rehaul
Can't be worked on right now without merge conflicts later
pr'd for
Soon™
question
Further information is requested
unimplemented
you can do this
Considered easy enough for someone's first PR.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: OpenWF/SpaceNinjaServer#828
No description provided.
Delete Branch "4dummies"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?