Skip to content

Add the donor list, a security policy & configuration for issue templates#4

Open
AR-DEV-1 wants to merge 7 commits intoRedot-Engine:masterfrom
AR-DEV-1:more-stuff
Open

Add the donor list, a security policy & configuration for issue templates#4
AR-DEV-1 wants to merge 7 commits intoRedot-Engine:masterfrom
AR-DEV-1:more-stuff

Conversation

@AR-DEV-1
Copy link
Contributor

@AR-DEV-1 AR-DEV-1 commented Mar 16, 2026

TL;DR

  • Adds donor list
  • Adds config for issue templates
  • Adds a security policy

Note

For now, the config has blank issues set to true until we make issue templates

Note

Contributed by 2LazyDevs.

Summary by CodeRabbit

Release Notes

  • Documentation
    • Updated GitHub issue template configuration to direct users to appropriate channels for feature proposals, documentation feedback, and technical support.
    • Added donor recognition documentation.

@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

📝 Walkthrough

Walkthrough

Adds three new repository files: GitHub issue template configuration, a donors acknowledgment document, and a security policy file; updates issue template behavior and contact links.

Changes

Cohort / File(s) Summary
GitHub issue template
.github/ISSUE_TEMPLATE/config.yml
New config enabling blank issues (blank_issues_enabled: true) and adding three contact_links for feature proposals, docs issues, and community support.
Donors document
DONORS.md
New content file listing donors, noting nonprofit context, and providing a Ko‑Fi donation link.
Security policy
SECURITY.md
New security policy describing vulnerability reporting contact (redotengine@gmail.com), PoC/video request, and expectations for report handling.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nibble on the changelog, bright and small,
Templates, donors, and safety — I recall.
A Ko‑Fi wink, a policy penned with care,
Community footprints scattered everywhere. 🐇✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes all main changes: adding donor list, security policy, and issue template configuration.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@AR-DEV-1 AR-DEV-1 marked this pull request as draft March 16, 2026 06:51
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
DONORS.md (1)

5-5: Consider shortening wording for readability.

Line 5 (“any and all”) is a bit wordy; a tighter phrase reads cleaner.

Suggested wording tweak
-Our Team greatly appreciates any and all donations.
+Our team greatly appreciates all donations.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@DONORS.md` at line 5, The sentence "Our Team greatly appreciates any and all
donations." is wordy; update the text (the line containing that exact string) to
a tighter phrasing such as "Our team greatly appreciates all donations." or "Our
team greatly appreciates any donation." and ensure capitalization is consistent
("team" lowercase) with project style.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@DONORS.md`:
- Around line 12-24: The donor names block is currently treated as a Markdown
code block due to four-space indentation; remove the leading four spaces from
the lines listing "Grom", "LionBox", "Mike K", etc., or convert them into a
proper Markdown list (prefix each entry with "-" or "*") so the entries render
as a readable list instead of a code block.

---

Nitpick comments:
In `@DONORS.md`:
- Line 5: The sentence "Our Team greatly appreciates any and all donations." is
wordy; update the text (the line containing that exact string) to a tighter
phrasing such as "Our team greatly appreciates all donations." or "Our team
greatly appreciates any donation." and ensure capitalization is consistent
("team" lowercase) with project style.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 55ad831d-1e75-4beb-a55b-961d526f9e2d

📥 Commits

Reviewing files that changed from the base of the PR and between 6800ede and d250e09.

📒 Files selected for processing (2)
  • .github/ISSUE_TEMPLATE/config.yml
  • DONORS.md

@AR-DEV-1 AR-DEV-1 marked this pull request as ready for review March 18, 2026 06:40
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
DONORS.md (1)

5-5: Optional: Consider simplifying "any and all".

The phrase "any and all donations" could be shortened to just "all donations" or "any donations" for conciseness, though the current phrasing emphasizes appreciation effectively.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@DONORS.md` at line 5, Replace the phrase "Our Team greatly appreciates any
and all donations." with a more concise alternative by editing the DONORS.md
line containing that exact sentence—e.g., change it to "Our team greatly
appreciates all donations." (also normalize capitalization of "Team" to "team"
if desired).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@SECURITY.md`:
- Line 7: In the SECURITY.md sentence that reads "To report a security
vulnerability that you found in Draconic, email us at `redotengine@gmail.com`.
Please provide a video (if possible) alonside a PoC (Proof of Concept).", fix
the typo by replacing "alonside" with "alongside" so the sentence reads
"...Please provide a video (if possible) alongside a PoC (Proof of Concept)."
- Around line 3-6: Remove the placeholder template text in SECURITY.md that
begins "Use this section to tell people how to report a vulnerability..." (the
generic instructional lines 3-6) and replace it with actual security disclosure
content or a concise reporting guideline; specifically delete the placeholder
sentences and add a short policy describing where to report vulnerabilities,
expected response times, and next steps (or leave the section blank if you
intend to add a full policy later).

---

Nitpick comments:
In `@DONORS.md`:
- Line 5: Replace the phrase "Our Team greatly appreciates any and all
donations." with a more concise alternative by editing the DONORS.md line
containing that exact sentence—e.g., change it to "Our team greatly appreciates
all donations." (also normalize capitalization of "Team" to "team" if desired).

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7a6feb07-7831-431d-84b4-57f1a9c9b380

📥 Commits

Reviewing files that changed from the base of the PR and between d250e09 and e574e3c.

📒 Files selected for processing (3)
  • .github/ISSUE_TEMPLATE/config.yml
  • DONORS.md
  • SECURITY.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/ISSUE_TEMPLATE/config.yml

AR-DEV-1 and others added 2 commits March 18, 2026 11:43
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@AR-DEV-1 AR-DEV-1 changed the title Add the donor list & configuration for issue templates Add the donor list, a security policy & configuration for issue templates Mar 18, 2026
Comment on lines +5 to +6
To report a security vulnerability that you found in Draconic, email us at `redotengine@gmail.com`. Please provide a video (if possible) alonside a PoC (Proof of Concept).
Thank you for helping us keep Draconic safe!

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To report a security vulnerability that you found in Draconic, email us at `redotengine@gmail.com`. Please provide a video (if possible) alonside a PoC (Proof of Concept).
Thank you for helping us keep Draconic safe!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove?

Copy link

@OldDev78 OldDev78 Mar 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw it repeated?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this line is repeated twice, which I assume is a typo.

@Arctis-Fireblight Arctis-Fireblight force-pushed the master branch 2 times, most recently from 0e50109 to 6800ede Compare March 20, 2026 23:49
Comment on lines +5 to +6
To report a security vulnerability that you found in Draconic, email us at `redotengine@gmail.com`. Please provide a video (if possible) alonside a PoC (Proof of Concept).
Thank you for helping us keep Draconic safe!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this line is repeated twice, which I assume is a typo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants