Skip to content

Conversation

@HennaAbbas
Copy link
Contributor

We no longer have a "my branches" filter ( we haven't for a while). We have "my builds". Updating the docs to reflect behavior in the CCI UI

You may find that there are errors for the vale/lint job that are unrelated to your change.
Vale checks the whole file when a change is made so if there are existing issues on the page they will be flagged.

You can just leave these errors and the CircleCI docs team will address them for you.
Vale logs are advisory to help all contributors create content that conforms to our style guide. The vale/lint job will not prevent changes from being published.

Description

What did you change?

Reasons

Why did you make these changes? What problem does this solve?

Content checks

Please follow our style when contributing to CircleCI docs. View our style guide or check out our CONTRIBUTING.md for more information.

Preview your changes:

  • To view the Vale linter results, select the ci/circleci: lint job at the bottom of your PR. You will be redirected to the vale/lint job output in CircleCI.
  • To preview your changes, select the ci/circleci: build job at the bottom of your PR and you will be redirected to CircleCI. Select the Artifacts tab and select index.html to open a preview version of the docs site built for your latest commit.

Take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs):

Content structure:

  • Break up walls of text by adding paragraph breaks.
  • Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
  • Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
  • Include relevant backlinks to other CircleCI docs/pages.

Formatting:

  • Keep the title between 20 and 70 characters.
  • Check all headings h1-h6 are in sentence case (only first letter is capitalized).

We no longer have a "my branches" filter ( we haven't for a while). We have "my builds". Updating the docs to reflect behavior in the CCI UI
@HennaAbbas HennaAbbas requested review from a team as code owners December 3, 2025 14:30

* *All builds in my projects* - you receive an email for every build in your project, whether it succeeds or fails.
* *My branches* - you receive an email when a build fails on a branch to which you have pushed changes.
* *My builds* - Send me an email every time a build I've pushed fails, and when it's fixed. Additionally, for Github and Bitbucket projects, include anyone's builds in branches I've pushed to before.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* *My builds* - Send me an email every time a build I've pushed fails, and when it's fixed. Additionally, for Github and Bitbucket projects, include anyone's builds in branches I've pushed to before.
* *My builds* - Send me an email every time a build fails that I triggered, and when it is fixed. Additionally, for Github and Bitbucket projects, include any builds on branches I have pushed to before.

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.

3 participants