shogun444 —
I tried applying to some open issues in Archestra's repo. It says only prior contributors can apply to issues. Is it how it's supposed to be?
#general
Hey, I've submitted a PR for issue #3218 — auto-sync permissions for Jira + Confluence. Would love any early feedback before review.
Hi everyone! I'm Harry, just joined the community. I've been looking at issue #4429 (automatic Pod restart on MCP server update). I've already done some local analysis and identified that
McpServerModel.update is missing the trigger to notify the runtime manager. I've also verified a fix with unit tests in mcp-server.test.ts. I'd love to take this on officially—is it okay if I /attempt it on GitHub?
I tried applying to some open issues in Archestra's repo.
It says only prior contributors can apply to issues.
Is it how it's supposed to be?
hey @user what are you thoughts on implementing semantic cashing in archestra ?
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!I tried applying to some open issues in Archestra's repo.
It says only prior contributors can apply to issues.
Is it how it's supposed to be?
7 replies
Hi! Yes, it works as designed. We require contributors to go through an onboarding. Every open issue should have a banner at the bttom, which redirects you to it.
👍1
thank you so much! for this useful information.
I noticed a few things.
When i went to the onboarding page and opened it in my phone.
The UI was breaking a bit.
I like this onboarding structure.
Many people nowadays use bots for even applying to issues and then flood the PR section with low-qualitu prs.
it's a great step for filtering contributors.
❤️1
I noticed a few things.When i went to the onboarding page and opened it in my phone.The UI was breaking a bit.
It will be amazing if you open an issue about this with a screenshot of what's actually breaking.
sure I will open an issue.
I opened the Issue.
I'd be happy to take this up if you'd like.