Individual counseling services offer a safe and supportive environment for individuals to work through personal challenges and improve their mental health and well-being. These services are typically provided by licensed mental health professionals and may be tailored to specific needs and goals. The counseling process may include various techniques such as cognitive-behavioral therapy, mindfulness, and talk therapy. https://www.annachandy.com/counselling.html

I've been surprised many times by the behavior of $ circleci tests split It would be great if we could see that code to determine how the splitting is working. I've ended up filing several one-off tickets asking for help, but every time I have an issue, I feel like I'm operating completely black-box, and would love to just look at the code myself, which I don't imagine would be sensitive/proprietary? The other code I'd love access to is whatever is transposing the junit XML assets into the json object that gets passed along as the timings file to subsequent builds. It seems like it may not take into account the difference between testsuite duration and aggregate testcase duration when determining how to split tests by filename -- so would save us a bunch of hassle to just understand that piece (and even contribute) if possible. Thanks for considering! CCI-I-244

There is no solid example on how to use dynamic configs. I am trying to use multiple configs.yml based on conditions.

I would love to see official documentation and/or support for pnpm on CircleCI. There is intention of adding a guide on the pnpm side ( https://github.com/pnpm/pnpm/issues/1648 ) but I feel it'd be better for CircleCI to officially support it rather than having a third-party come up with that. And with pnpm gaining traction–specially with developers working on monorepos–over npm and yarn (because of its performance) I feel it'd be the smart move. Thanks!

This is minor but would really make our team happy. Most of the built-in steps we use have infinitive case (e.g. "Spin up environment", "Check out code") but a few use the gerund form (e.g. "Preparing environment variables..." or "Restoring cache..."). Consistency is a big deal and this would be an easy fix to improve it greatly, to have all the built-in steps use consistent infinitive case (e.g. update to "Prepare environment variables", "Restore cache"...)

There appears to be more than one Windows executor version but no documentation on what the versions are, what the differences are, how often they are upgraded, etc. Really the only mention of the Windows setup is in the Hello World page.

A training plan and test platform to understand the user's knowledge level on CircleCI and CI/CD. CCI-I-1121

Anecdotally, the v2 api appears to treat project slug in a case-sensitive manner. This very well may be side effect of its placement in the path of the URI ( https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-25#section-2.7.3 ) for the API resources I've tested against. Regardless, I'm unable to find a clear statement in the v2 docs whether or not slug is case-sensitive. https://discuss.circleci.com/t/github-case-insensitive-org-name/23899 hints that this has been a source of confusion for a while.

The CircleCI server docs are available as a PDF. Can we make the CircleCI cloud docs available as a single PDF as well? For example, many AWS docs are available as a single PDF. PDF files are great for ereaders, and allow highlighting, note taking, commenting, etc. CCI-I-1462

I'm thinking of how Google organizes API REST response equivalent information pertaining to a resource that you are looking at. For example, where you can access various resources via the API. So if I look at an image, for example, it shows me the URL of that image, etc. Great product, but for a new user, the endpoints you provide are kinda hard to digest from documentation alone, so I've been spending too much time trying to troubleshoot. Working backwards, and having the specific information that I need to GET artifacts, for example, is a more intuitive way to learn your API, imo. CCI-I-972