Git#1
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="changelog.md">
<violation number="1" location="changelog.md:7">
P3: Inconsistent command formatting: "Hide / search" has a space between `/` and `search`, unlike every other command reference in the changelog (e.g., `/search`, `/chronicle`, `/model`, `/agent`). Remove the space to match the established convention.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| - Show a single Error prefix for mcp and skill command failures | ||
| - Show the real parse error when --agent selects a malformed custom agent | ||
| - web_fetch works through mandatory HTTPS proxies | ||
| - Hide / search on the Gists tab |
There was a problem hiding this comment.
P3: Inconsistent command formatting: "Hide / search" has a space between / and search, unlike every other command reference in the changelog (e.g., /search, /chronicle, /model, /agent). Remove the space to match the established convention.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At changelog.md, line 7:
<comment>Inconsistent command formatting: "Hide / search" has a space between `/` and `search`, unlike every other command reference in the changelog (e.g., `/search`, `/chronicle`, `/model`, `/agent`). Remove the space to match the established convention.</comment>
<file context>
@@ -1,3 +1,53 @@
+- Show a single Error prefix for mcp and skill command failures
+- Show the real parse error when --agent selects a malformed custom agent
+- web_fetch works through mandatory HTTPS proxies
+- Hide / search on the Gists tab
+- Treat superseded subagent runs as cancellations instead of failures
+- Add paginated session.mcp.resources read/list/listTemplates RPCs for MCP server resources
</file context>
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
13 participants
GitHub Community Guidelines
Millions of developers across the world host millions of projects—both open and closed source—on GitHub. We're fortunate to be able to play a part in enabling collaboration across the developer community every day, which is a responsibility we don’t take lightly. Together, we all have the exciting opportunity to make this a community we can be proud of.
Our diverse user base brings different perspectives, ideas, and experiences, and ranges from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub an environment that welcomes all the different voices and perspectives our community has to offer, while maintaining a safe place for developers to do their best work.
By outlining what we think a safe, welcoming, and productive community looks like at GitHub, we hope to help you understand how best to interact and collaborate on our platform in line with our Terms of Service and Acceptable Use Policies.
We encourage our community members to communicate expectations clearly, moderate their projects where possible, and report any content that may violate our policies. GitHub Staff will investigate any reports of abuse, and may moderate public content on our site that we determine to be in violation of our Terms of Service.
Maintaining a strong community
The primary purpose of the GitHub community is to collaborate on software projects. We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. At the same time, it's important that users remain respectful and allow space for others to contribute openly. In order to foster both a safe and productive environment, we encourage our community members to look to these guidelines to inform how they interact on our platform. Below, you’ll find some suggestions for how to have successful interactions as a valued member of the GitHub community.
Be welcoming and open-minded - New users join our community each day. Some are well-established developers, while others are just beginning. Be open to other ideas and experience levels. Make room for opinions other than your own and be welcoming to new collaborators and those just getting started.
Be respectful - Working in a collaborative environment means disagreements may happen. But remember to criticize ideas, not people. Share thoughtful, constructive criticism and be courteous to those you interact with. If you’re unable to engage respectfully, consider taking a step back or using some of our moderation tools to deescalate a tense situation.
Be empathetic - GitHub is a global community with people from a wide variety of backgrounds and perspectives, many of which may not be your own. Try to put yourself in others’ shoes and understand their feelings before you address them. Do your best to help make GitHub a community where others feel safe to make contributions, participate in discussions, and share different ideas.
What if something or someone offends you?
While some disagreements can be resolved with direct, respectful communication between community members, we understand that is not always the case. We encourage our community to contact GitHub Support through the GitHub Support portal when they believe content or activity they’ve encountered violates our policies. However, if you run into something or someone on the site that you find objectionable, here are some ways GitHub enables you to take action:
Communicate expectations - Maintainers can set community-specific guidelines to help users understand how to interact with their projects, for example, in a repository’s README, CONTRIBUTING file, or dedicated code of conduct. You can find additional information on building communities on the Communities page.
Moderate Comments - Users with write-access privileges for a repository can edit, delete, or hide anyone's comments on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can also delete sensitive information from a comment's edit history. Moderating your projects can feel like a big task if there is a lot of activity, but you can add collaborators to assist you in managing your community.
Lock Conversations - If a discussion in an issue, pull request, or commit gets out of hand, off topic, or violates your project’s code of conduct or GitHub’s policies, owners, collaborators, and anyone else with write access can put a temporary or permanent lock on the conversation. For more information, see Locking conversations.
Block Users - If you encounter a specific user who you would rather not engage with, you can block the user from your personal account or from your organization.
Limit Interactions - If your public project is getting unwanted attention, being trolled, spammed, or otherwise, you have the option of setting temporary interaction limits to keep certain users from interacting with your repository. You can even set code review limits to ensure quality contributions on your projects.
While we are passionate about empowering maintainers to moderate their own projects, please contact us through the GitHub Support portal if you need additional support in dealing with a situation.
What happens if someone violates GitHub's policies?
We rely on reports from the community, as well as proactive detection, to help ensure that GitHub is a safe, welcoming, and productive platform for software developers. There are a variety of factors we consider when we’re made aware of behavior or content not in line with GitHub’s policies. However, our policy enforcement and content moderation approach prioritizes our vision to be the home for all developers. This means:
We optimize for code collaboration. We recognize that code can have multiple uses and we distinguish between how the code is being used on the platform and other possible uses. We also think about how our enforcement actions can affect a potentially complicated web of interdependencies across the platform and aim to restrict as little legitimate content as possible.
We take a human-centered approach to content moderation and we tailor our responses to meet the needs of a specific situation. Our global team investigates the reports we receive on a case-by-case basis—considering context and the surrounding facts—before taking action. This could include taking into account potentially offensive content being posted in a way that lacks context or makes it easy for other users to unwittingly view or interact with while using GitHub. In those instances, we may favor moderation in order to safeguard our community.
Our decisions are rooted in our core belief that serving an interconnected community and empowering human progress through developer collaboration requires a commitment to diversity, inclusion, and belonging.
Where we have decided that moderation action is warranted, these are some of the ways we may respond:
Appeal and Reinstatement
If your content or account has been disabled or restricted and you seek reinstatement or wish to appeal, please see our Appeal and Reinstatement page for information about the process and use our Appeal and Reinstatement form to submit a request.
Legal Notices
We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of CC0-1.0.
These are only guidelines; they do not modify our Terms of Service and are not intended to be a complete list. Under those terms, GitHub retains full discretion to remove any content or terminate any accounts for activity that violates our Acceptable Use Policies. These guidelines describe when we will exercise that discretion.``
Summary by cubic
Updates
changelog.mdwith releases 1.0.48–1.0.71. 1.0.71 adds safer plan mode, plugin marketplace management, session persistence, MCP and sandbox improvements, and multiple UX and reliability fixes.plugins marketplacelist/add/remove plus browse and update commands;copilot plugin listshows--plugin-dirplugins.--sandbox/--no-sandboxignored warnings on interactive startup.copilot -p --autopilotnow honorsCOPILOT_TASK_WAIT_TIMEOUT_SECONDSinstead of hanging./modeland pickers, case‑insensitive slash commands, clearer errors; add/voice devicesto choose and persist the microphone.Written for commit fd24cea. Summary will update on new commits.