You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Label note: the in-progress label does not exist in this repo and QuasarAppCI cannot create labels (no admin permission) — status is tracked via this comment thread instead.
Milestone #1 "Comunity Release" open issues: #7 (closed by @EndrII 16:20Z), #8, #9, #12, #13. All are ready to be closed, but the QuasarAppCI account has read-only (pull) access on this repository and cannot close issues or manage labels:
GraphQL CloseIssue -> "does not have the correct permissions"
REST state=closed -> 403 "Must have admin rights to Repository"
label create/apply -> 404 (no admin permission)
Delivered PR #14: a one-shot, maintainer-triggered workflow (workflow_dispatch only, GITHUB_TOKEN with issues: write + milestones: write) that closes all open issues of milestone #1 and then the milestone itself, and prints the final state.
Update: PR #14 was closed unmerged per @EndrII's feedback ("release means close all issues in milestone. This workflow is not required"); the task_13 branch was deleted.
The remaining blocker is unchanged: QuasarAppCI has read-only (pull) access on this repo and cannot close issues or manage labels (verified: CloseIssue denied, REST 403, label API denied). Please either close #8, #9, #12, #13 + milestone #1 directly, or grant QuasarAppCI maintain permission and I will complete it in the next cycle.
7. Update: PR #14 was closed unmerged per @EndrII's feedback ("release means close all issues in milestone. This workflow is not required"); the task_13 branch was deleted.
The remaining blocker is unchanged: QuasarAppCI has read-only (pull) access on this repo and cannot close issues or manage labels (verified: CloseIssue denied, REST 403, label API denied). Please either close #8, #9, #12, #13 + milestone #1 directly, or grant QuasarAppCI maintain permission and I will complete it in the next cycle.
you should not close this issues directly - you must resolve it - and create pull request for each issues. with "fix" links.
Per @EndrII's instruction (17:01Z): the milestone issues must be resolved, each with its own pull request carrying a "Fixes" link — not closed directly. The PR #14 workflow approach is dropped.
Plan — four branches strictly from main (b4be1e9), four PRs to this repository:
task_8 — resolve Update readme #8 "Update readme": rewrite README.md (main points of this fork: performance oriented, C-only implementation; Rust removed — slow, 32 bit source; upstream maintainers inactive; other languages via simple wrapper + Merge Request; remove irrelevant upstream data; add proper C/C++ + CMake usage examples) → PR with Fixes #8
task_9 — resolve Change Liense to LGPLv3 #9 "Change Liense to LGPLv3": LICENSE → LGPLv3 with copyright QuasarApp Group DOO, remove UNLICENSE, update build-file license header → PR with Fixes #9
task_12 — resolve Implement GitHub Page #12 "Implement GitHub Page": MkDocs + Material documentation site (same style as Heart #88, different colors), README as home page, Doxygen API under /api/, deploy workflow to the gh-pages branch → PR with Fixes #12
task_13 — resolve Comunity Release #13: release changelog for the "Comunity Release" milestone → PR with Fixes #13
Local verification: CMake build + test target; Doxygen + MkDocs site build
git diff check per branch, push to the QuasarAppCI fork, open the four PRs
CI green on all four PRs
Final comment + mark the notification read
Label note: the in-progress label does not exist in this repo and QuasarAppCI cannot create labels (no admin permission, re-verified) — status is tracked in this thread.
Quasar Agent — issue_13: resolution complete, 4 PRs published
Per the instruction "you should not close this issues directly - you must resolve it - and create pull request for each issues with 'fix' links", every open issue of the "Comunity Release" milestone is resolved individually — one branch from main (b4be1e9) and one PR per issue, each PR body carrying the Fixes #N link so the issue auto-closes on merge:
GitHub Pages site by analogy with QuasarApp/Heart (teal palette instead of maroon): MkDocs + Material, Doxygen API output under /api/, deploy-docs.yml deploying to the gh-pages branch, generated artifacts gitignored
Close milestone Improve rust speed #1 "Comunity Release" — it has no open issues left after the merges, but the milestone itself needs one maintainer click (no milestone permission on this account).
After the first deploy (the deploy-docs.yml workflow runs on the push to main when PR Add GitHub Pages documentation site (issue 12) #17 merges): configure GitHub Pages in the repository settings — source: branch gh-pages, path /.
Notification 26313128804 marked as read. No local tmp/build artifacts left behind.
Merge attempts are still rejected: QuasarAppCI does not have the correct permissions to execute MergePullRequest (3 attempts, latest ~18:55Z); repo access is still pull-only — the permission grant may not have propagated yet.
Once write/maintain permission on QuasarApp/OpenSimplex2 is effective I will merge #15 → #16 → #18 (each carries a Fixes #N link, so #8/#9/#13 auto-close), verify the gh-pages deploy, and close out. Notification thread left open until the merges land.
Activity
QuasarAppCI commentedon Oct 13, 2026
Quasar Agent — Task issue_13 checklist (initial)
Working on "Comunity Release" — closing the milestone #1 "Comunity Release" with all its issues, per the issue instruction.
git pull(main up to date at b4be1e9)Label note: the
in-progresslabel does not exist in this repo and QuasarAppCI cannot create labels (no admin permission) — status is tracked via this comment thread instead.QuasarAppCI commentedon Oct 13, 2026
Quasar Agent — issue_13: progress + permission blocker
Milestone #1 "Comunity Release" open issues: #7 (closed by @EndrII 16:20Z), #8, #9, #12, #13. All are ready to be closed, but the QuasarAppCI account has read-only (pull) access on this repository and cannot close issues or manage labels:
CloseIssue-> "does not have the correct permissions"state=closed-> 403 "Must have admin rights to Repository"Delivered PR #14: a one-shot, maintainer-triggered workflow (
workflow_dispatchonly, GITHUB_TOKEN withissues: write+milestones: write) that closes all open issues of milestone #1 and then the milestone itself, and prints the final state.@EndrII — please pick one:
QuasarAppCIaccount maintain permission — I will close Update readme #8, Change Liense to LGPLv3 #9, Implement GitHub Page #12, Comunity Release #13 and milestone Improve rust speed #1 directly in the next cycle, or(Label note: "help wanted" / "needs-clarification" could not be added — no label permission on this repo.)
QuasarAppCI commentedon Oct 13, 2026
Update: PR #14 was closed unmerged per @EndrII's feedback ("release means close all issues in milestone. This workflow is not required"); the
task_13branch was deleted.The remaining blocker is unchanged: QuasarAppCI has read-only (pull) access on this repo and cannot close issues or manage labels (verified:
CloseIssuedenied, REST 403, label API denied). Please either close #8, #9, #12, #13 + milestone #1 directly, or grant QuasarAppCI maintain permission and I will complete it in the next cycle.EndrII commentedon Oct 13, 2026
you should not close this issues directly - you must resolve it - and create pull request for each issues. with "fix" links.
QuasarAppCI commentedon Oct 13, 2026
Quasar Agent — Task issue_13 checklist (round 2)
Per @EndrII's instruction (17:01Z): the milestone issues must be resolved, each with its own pull request carrying a "Fixes" link — not closed directly. The PR #14 workflow approach is dropped.
Plan — four branches strictly from
main(b4be1e9), four PRs to this repository:task_8— resolve Update readme #8 "Update readme": rewrite README.md (main points of this fork: performance oriented, C-only implementation; Rust removed — slow, 32 bit source; upstream maintainers inactive; other languages via simple wrapper + Merge Request; remove irrelevant upstream data; add proper C/C++ + CMake usage examples) → PR withFixes #8task_9— resolve Change Liense to LGPLv3 #9 "Change Liense to LGPLv3": LICENSE → LGPLv3 with copyright QuasarApp Group DOO, remove UNLICENSE, update build-file license header → PR withFixes #9task_12— resolve Implement GitHub Page #12 "Implement GitHub Page": MkDocs + Material documentation site (same style as Heart #88, different colors), README as home page, Doxygen API under/api/, deploy workflow to thegh-pagesbranch → PR withFixes #12task_13— resolve Comunity Release #13: release changelog for the "Comunity Release" milestone → PR withFixes #13testtarget; Doxygen + MkDocs site buildgit diffcheck per branch, push to the QuasarAppCI fork, open the four PRsLabel note: the
in-progresslabel does not exist in this repo and QuasarAppCI cannot create labels (no admin permission, re-verified) — status is tracked in this thread.QuasarAppCI commentedon Oct 13, 2026
Quasar Agent — issue_13: resolution complete, 4 PRs published
Per the instruction "you should not close this issues directly - you must resolve it - and create pull request for each issues with 'fix' links", every open issue of the "Comunity Release" milestone is resolved individually — one branch from
main(b4be1e9) and one PR per issue, each PR body carrying theFixes #Nlink so the issue auto-closes on merge:CMakeLists.txt+OpenSimplex2Interface), manual build + test target usage, license section; upstream-only data removedCopyright (C) 2026 QuasarApp Group DOO; rootUNLICENSEremoved (hlsl/UNLICENSEkept for the existing third-party-derived HLSL code); CMake header comments updated/api/,deploy-docs.ymldeploying to thegh-pagesbranch, generated artifacts gitignoredCHANGELOG.mddocumenting the "Comunity Release" milestoneCI (Linux + Windows build and test) is green on all four PRs.
Remaining maintainer steps (the QuasarAppCI account has pull-only access on this repo):
deploy-docs.ymlworkflow runs on the push tomainwhen PR Add GitHub Pages documentation site (issue 12) #17 merges): configure GitHub Pages in the repository settings — source: branchgh-pages, path/.Notification
26313128804marked as read. No local tmp/build artifacts left behind.EndrII commentedon Oct 13, 2026
You may merge rest of this changes
QuasarAppCI commentedon Oct 13, 2026
Quasar Agent — issue_13: merge prep complete, awaiting merge permission
Per "You may merge rest of this changes" (18:47Z):
QuasarAppCI does not have the correct permissions to execute MergePullRequest(3 attempts, latest ~18:55Z); repo access is still pull-only — the permission grant may not have propagated yet.Once write/maintain permission on QuasarApp/OpenSimplex2 is effective I will merge #15 → #16 → #18 (each carries a
Fixes #Nlink, so #8/#9/#13 auto-close), verify thegh-pagesdeploy, and close out. Notification thread left open until the merges land.QuasarAppCI commentedon Oct 13, 2026
Quasar Agent — issue_13: "Comunity Release" shipped ✅
All remaining PRs are merged into
main(5b1d69c):Issues #8, #9 and #13 are closed (auto-closed via the
Fixes #Nlinks).Post-merge verification on
main:testtarget 3/3 passing.deploy-docs.ymlsucceeded on push to main andpages-build-deploymentforgh-pagessucceeded — the site content is on the branch.Two remaining maintainer steps (QuasarAppCI account still lacks these permissions):
PATCH /milestones/1→ 404 for this account).gh-pages, path/(per PR Add GitHub Pages documentation site (issue 12) #17).