I want to be able to define an entire workflow in an orb, using the jobs of my orb and allowing parameters to conditionally choose which jobs to run and allow parameterization of branch and tag filters as well. CCI-I-615

Allow the deletion of private orbs so users can stay within their orb limits. Private orbs have a limited scope of users, so if the owner is aware of the risks of breaking internal CI pipelines then they should have the option to delete orbs as necessary.

It'd be useful to allow handling lists of values for a parameter, without having to resort to workarounds like parsing comma-separated lists in string types. I think it would be useful to be able to specify something like: steps: - myorb/foo: bar: - baz - qux And have the myorb/foo command called with a bar parameter equal to [ "baz", "qux" ] . CCI-I-701

As a user who has projects spread across multiple organizations, it would be helpful if an org could be allowed to use a private orb from another org.

Could be a project level API key with publishing permissions, or use team membership like contexts do. Some means to expand the population of folks who can deploy prod versions of orbs without giving them global admin rights in GH. CCI-I-1108

We're encountering more use cases where customers want centrally managed configurations that can be called and used. For example, many projects may follow the exact same workflows, and any updates to a process need to be reflected in all projects. Orbs are a step in the right direction, but each project must still manually update the orb version to see new changes - a centralized change does not propagate automatically. Maybe if we added a "latest" tag for orbs? We also don't yet support templatizing workflows in orbs, so we still have to write a lot of config. Related ideas: https://ideas.circleci.com/orbs/p/workflows-in-orbs

Is it possible for me to have someone train me in a vigilante misson to catch child molesters useing this platform???can we develop an AI thats in a package to be and under aged girl on Snapchat or similar form I wanna help be a part of cleaning up our local streets and save woman such as my biological sister who was molested as a child if anyone can possibly point me in the right direction I would appreciate that thanks...I am getting a team together to help also but without a program I think it's gonna way less sufficient thanks! for your time Krizmer Rees

In a single-file orb a developer can define some top-level parameters as yaml anchors and re-use them within different steps/jobs/workflows. This is a very handy tool for keeping the config file DRY. However, this feature does not appear to be supported when using the orb development kit. I propose that anchors should be able to be defined in the @orb.yml alongside other top-level config values. Example @orb.yml: version: 2.1 description: > Example for CircleCI orbs: aws-s3: circleci/aws-s3@2.1 awesome_param: &awesome_param description: >- Set to true if awesome. type: boolean default: true

Team, I did reach out to circle ci customer support for configuring slack notification on workflow fail/ pass. But after trying multiple solutions provided by Josh and team, we failed to achieve it. So please provide this feature. Requirement: Slack notification on workflow fail/ pass event Use case: Regression has multiple job setup to execute automation test cases in 5 containers. So once this jobs are completed I would like to receive a notification each job status in one line expected output: workflow master-regression failed Jobs: goals2019 - failed, rtf email_rtf- passed, profile- failed

Currently "Allow Uncertified Orbs" of "Orb Security Settings" have binary option to allow to use third-party orbs or not.We wish to use WHITE LIST orb provider. CCI-I-687