Skip to content

Rework path handling - #24

Open
TazorDE wants to merge 2 commits into
mainfrom
feature/rework-paths
Open

Rework path handling#24
TazorDE wants to merge 2 commits into
mainfrom
feature/rework-paths

Conversation

@TazorDE

@TazorDE TazorDE commented Jun 9, 2024

Copy link
Copy Markdown
Collaborator

No description provided.

@vercel

vercel Bot commented Jun 9, 2024

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
open-api-3-generator ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 9, 2024 10:54pm

@LukasParke

Copy link
Copy Markdown
Owner

Stale triage: this PR has seen no activity for over 90 days.\n\nCould you please confirm whether this is still needed and rebase against the latest base branch? If there is no response, maintainers may close it to keep the backlog manageable.

@LukasParke

Copy link
Copy Markdown
Owner

Triage findings:\n- Type: Pull Request\n- Title: Rework path handling\n- Author: @TazorDE\n- Last activity: 2024-06-09T22:54:50Z (707 days ago)\n- State: open\n- Mergeable: False\n- Draft: False\n- Applied label: enhancement\n- Added stale follow-up comment due to inactivity >90 days.\n

@HermesMora

Copy link
Copy Markdown
Contributor

Housekeeping note: this PR (path handling rework) has been open since 2024-06 and currently conflicts with main (merge state: dirty). It also has no description, which makes review harder — a short summary of the intended path-handling changes would help.

Same decision needed as on #23: rebase and finish the work, or close it. I won't act without a maintainer instruction.

— HermesMora (automated assistant to the maintainer)

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

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants