Skip to content

Add Planka #503

Open
theZasa wants to merge 8 commits into
mainfrom
planka
Open

Add Planka #503
theZasa wants to merge 8 commits into
mainfrom
planka

Conversation

@theZasa

@theZasa theZasa commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

Description

add PLANKA to USE

Summary by CodeRabbit

  • Documentation
    • Added complete documentation and metadata for PLANKA, a collaborative Kanban-based project management application. Documentation includes software information, licensing details, and feature descriptions covering visual workflow organization, task prioritization, customizable boards, drag-and-drop task management, real-time team collaboration, and container-based deployment support.

@theZasa theZasa requested a review from klml April 14, 2026 16:55
@coderabbitai

coderabbitai Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@theZasa has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 51 minutes and 0 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 51 minutes and 0 seconds.

⌛ 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.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 694ed126-2213-4b6d-859c-2097c450be5c

📥 Commits

Reviewing files that changed from the base of the PR and between 090dee8 and 14d2458.

📒 Files selected for processing (2)
  • de/software/planka.md
  • software/planka.md

Walkthrough

A new documentation file for PLANKA software was added, containing metadata (title, developer, source URL, licensing information, tags) and German descriptive content characterizing it as a collaborative Kanban-based project management tool.

Changes

Cohort / File(s) Summary
PLANKA Documentation
software/planka.md
Added new software metadata and documentation file with front-matter fields and German descriptions of PLANKA's features as a collaborative Kanban project management tool.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add Planka' directly and accurately describes the main change: adding documentation for the PLANKA software to the repository.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch planka

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@software/planka`:
- Around line 5-6: The front-matter has conflicting fields: `licensingmodel` is
set to "Open Source" while `license` is "Fair Use License"; update them to be
consistent by either replacing `licensingmodel: Open Source` with a
source-available classification like `licensingmodel: Source-available` to match
`license: Fair Use License`, or change `license` to an OSI-approved license
(e.g., MIT) if you intend to keep `licensingmodel: Open Source`; ensure both
`licensingmodel` and `license` reflect the same classification.
- Line 1: The file named "software/planka" is extensionless and located in the
wrong language folder, so VitePress will skip it; either remove this
extensionless file if the English markdown is sufficient, or rename/move it to
"de/software/planka.md" and give it a .md extension so the German variant is
discovered by the existing glob (software/*.md and de/software/*.md); ensure the
file content remains German after moving and update any internal links or
frontmatter if present.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2f62b9af-1a8b-43b7-8bbe-b928712fa328

📥 Commits

Reviewing files that changed from the base of the PR and between 244c5f0 and 090dee8.

📒 Files selected for processing (2)
  • software/planka
  • software/planka.md
📜 Review details
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-03-05T07:22:13.719Z
Learnt from: klml
Repo: it-at-m/opensource.muenchen.de PR: 479
File: software/openapi-generator.md:8-8
Timestamp: 2026-03-05T07:22:13.719Z
Learning: In software/* front matter (Markdown) within this repo, allow the sponsor field to point to the project’s main website when the Sponsors section on that site is the intended destination and there is no fragment/link to a specific sponsor page. Do not flag the main project URL as incorrect in this case. If a dedicated sponsorship/donation page exists and a specific sponsor anchor could be linked, prefer that URL.

Applied to files:

  • software/planka.md
🔇 Additional comments (2)
software/planka.md (2)

5-6: Same licensing-model mismatch as in software/planka.

Line 5 (open source) and Line 6 (Fair Use License) carry the same classification conflict already raised above; please apply the same correction here for consistency.


13-21: Content quality looks good.

The English description is clear, accurate in scope, and readable for a software catalog entry.

Comment thread software/planka
@@ -0,0 +1,21 @@
---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify whether software entries are expected to be .md files and whether extensionless files exist.
fd . software
echo "---- markdown entries ----"
fd -e md . software | sort
echo "---- extensionless entries in software/ ----"
find software -maxdepth 1 -type f ! -name "*.md" -print | sort
echo "---- references to software content-loading conventions ----"
rg -n -C2 'software/|\\.md|front matter|contentDir|collections|glob' README.md **/*.yml **/*.yaml **/*.toml **/*.json **/*.js **/*.ts 2>/dev/null

Repository: it-at-m/opensource.muenchen.de

Length of output: 6497


🏁 Script executed:

#!/bin/bash
# Find build/config files that might define how content is ingested
echo "=== Looking for build configuration files ==="
fd -e js -e ts -e yml -e yaml -e toml -e json -e mjs -e cjs | grep -E '(config|build|astro|gatsby|next|eleventy|hugo|jekyll)' | head -20

echo -e "\n=== Build config files in root ==="
ls -la | grep -E '(^\\.|config|build)'

echo -e "\n=== Checking for package.json and scripts ==="
if [ -f package.json ]; then
  cat package.json | head -50
fi

echo -e "\n=== Looking for site generator indicators ==="
fd -e txt README | xargs grep -l "build\|static\|site generation" 2>/dev/null || true

Repository: it-at-m/opensource.muenchen.de

Length of output: 756


🏁 Script executed:

#!/bin/bash
# Compare the two planka files to understand their relationship
echo "=== Contents of software/planka (extensionless) ==="
head -20 software/planka

echo -e "\n=== Contents of software/planka.md (with extension) ==="
head -20 software/planka.md

echo -e "\n=== File sizes ==="
ls -lh software/planka*

echo -e "\n=== Are they identical? ==="
if cmp -s software/planka software/planka.md; then
  echo "Files are IDENTICAL"
else
  echo "Files are DIFFERENT"
  echo "--- Diff ---"
  diff software/planka software/planka.md | head -30
fi

Repository: it-at-m/opensource.muenchen.de

Length of output: 3653


🏁 Script executed:

#!/bin/bash
# Search for any build/content configuration patterns
echo "=== Looking for contentDir or glob patterns in config files ==="
rg -l 'contentDir|glob|import.*software|content.*glob|include|exclude|pages' . --type ts --type js --type json --type yaml --type toml 2>/dev/null | head -10

echo -e "\n=== Checking .gitignore for patterns ==="
if [ -f .gitignore ]; then
  cat .gitignore | grep -E 'software|md|file|extension' || echo "No relevant patterns found"
fi

echo -e "\n=== File timestamps and git info ==="
ls -l software/planka* 2>/dev/null
echo "--- Git status ---"
git status software/planka* 2>/dev/null || echo "Not in git or git unavailable"

Repository: it-at-m/opensource.muenchen.de

Length of output: 480


🏁 Script executed:

#!/bin/bash
# Look for VitePress configuration
echo "=== VitePress config files ==="
fd -e ts -e js -e mts -e mjs | grep -i vitepress

echo -e "\n=== .vitepress directory contents ==="
ls -la .vitepress/ 2>/dev/null | head -20 || echo "No .vitepress dir or not accessible"

echo -e "\n=== Checking docs structure ==="
fd -e md . --max-depth 2 | head -15

echo -e "\n=== Checking for docs/software directory ==="
ls -la docs/ 2>/dev/null | head -20 || echo "No docs directory"

echo -e "\n=== Looking for content glob patterns or markdown processing ==="
rg -i 'src.*glob|include.*md|extend.*md|processMarkdown' . --type ts --type js 2>/dev/null | head -10 || echo "No patterns found"

Repository: it-at-m/opensource.muenchen.de

Length of output: 935


🏁 Script executed:

#!/bin/bash
echo "=== Contents of software.data.js (English loader) ==="
cat .vitepress/software.data.js

echo -e "\n=== Contents of software-de.data.js (German loader) ==="
cat .vitepress/software-de.data.js

echo -e "\n=== Relevant section of config.mts ==="
head -100 .vitepress/config.mts

Repository: it-at-m/opensource.muenchen.de

Length of output: 4020


🏁 Script executed:

#!/bin/bash
# Check if software directory is referenced in config
echo "=== Searching for 'software' in config.mts ==="
rg -n 'software' .vitepress/config.mts

echo -e "\n=== Searching for file loading patterns in config.mts ==="
rg -n 'glob|readFile|fs\.|import.*software' .vitepress/config.mts

Repository: it-at-m/opensource.muenchen.de

Length of output: 306


Remove software/planka (extensionless) or rename it to de/software/planka.md.

VitePress loads software content using glob patterns that require .md extensions: software/*.md for English and de/software/*.md for German. The extensionless software/planka file will be skipped entirely during the build. The file also contains German content but is placed in the wrong directory. Either delete it if the English version suffices, or move it to de/software/planka.md to make the German variant available.

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

In `@software/planka` at line 1, The file named "software/planka" is extensionless
and located in the wrong language folder, so VitePress will skip it; either
remove this extensionless file if the English markdown is sufficient, or
rename/move it to "de/software/planka.md" and give it a .md extension so the
German variant is discovered by the existing glob (software/*.md and
de/software/*.md); ensure the file content remains German after moving and
update any internal links or frontmatter if present.

Comment thread software/planka
Comment on lines +5 to +6
licensingmodel: Open Source
license: Fair Use License

@coderabbitai coderabbitai Bot Apr 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Fix license classification mismatch in front matter.

Line 5 (licensingmodel: Open Source) conflicts with Line 6 (license: Fair Use License). Fair Use License is generally treated as fair-code/source-available, not OSI open source. This metadata mismatch can misclassify the entry in generated lists/filters.

Proposed metadata fix
-licensingmodel: Open Source
+licensingmodel: Source Available
 license: Fair Use License
📝 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.

Suggested change
licensingmodel: Open Source
license: Fair Use License
licensingmodel: Source Available
license: Fair Use License
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@software/planka` around lines 5 - 6, The front-matter has conflicting fields:
`licensingmodel` is set to "Open Source" while `license` is "Fair Use License";
update them to be consistent by either replacing `licensingmodel: Open Source`
with a source-available classification like `licensingmodel: Source-available`
to match `license: Fair Use License`, or change `license` to an OSI-approved
license (e.g., MIT) if you intend to keep `licensingmodel: Open Source`; ensure
both `licensingmodel` and `license` reflect the same classification.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@klml can you fix the license?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

Comment thread de/software/planka.md
developer: PLANKA Community
code: https://github.com/plankanban/planka
licensingmodel: Open Source
license: Fair Use License

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@klml welche lizenz?

Comment thread software/planka.md
developer: PLANKA Community
code: https://github.com/plankanban/planka
licensingmodel: open source
license: Fair Use License

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

siehe oben @klml

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.

1 participant