Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Change conan v2 feedback message #19522

Merged

Conversation

uilianries
Copy link
Member

Following Conan 2.x migration schedule. From now, all PRs should pass by Conan 2.x CI build.

More information in #19104

Most of recipes are ported now to Conan 2.x, and the recommendation for those that are still missing is pinging us in the PR, so we can help to migrate it too.

This PR only updates the feedback message, not the CI behavior. The behavior should be done in a separated PR.

/cc @jcar87 @danimtb @RubenRBS


Signed-off-by: Uilian Ries <uilianries@gmail.com>
regression: "> **Regression**: Conan v2 builds are mandatory and they are required for the PR to be merged, because this recipe worked with Conan v2 previously."
text_on_failure: "The v2 pipeline failed. Please, review the errors and note this will be required for pull requests to be merged in the near future."
text_on_failure: "The v2 pipeline failed. Please, review the errors and note this is required for pull requests to be merged. In case this recipe is still not ported to Conan 2.x, please, comment on the PR and we will help you."
Copy link
Member

@danimtb danimtb Aug 31, 2023

Choose a reason for hiding this comment

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

maybe we need a more specific message to ask for help. Maybe a gh mention with "@___" do we have a @<maintainers> group?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, so far we have Barbarians group, but it alerts everyone. We could provide another group. As groups are created by organization, @maintainers would be too generic, what about @cci-maintainers then?

Copy link
Member

Choose a reason for hiding this comment

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

let's start with @conan-io/barbarians

Copy link
Member Author

Choose a reason for hiding this comment

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

Done, included conan/barbarians

Copy link
Contributor

Choose a reason for hiding this comment

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

You wont get notifications from non-members of the group AFAIK on GitHub

Copy link
Member Author

Choose a reason for hiding this comment

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

@prince-chrismc I didn't know about that. Checking the documentation, it seems we can configure notifications: https://docs.github.com/en/organizations/organizing-members-into-teams/configuring-team-notifications

Copy link
Contributor

Choose a reason for hiding this comment

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

Ohhh perfect! Glad they changed that

Signed-off-by: Uilian Ries <uilianries@gmail.com>
AbrilRBS
AbrilRBS previously approved these changes Sep 1, 2023
.c3i/config_v2.yml Outdated Show resolved Hide resolved
Co-authored-by: Daniel <danimanzaneque@gmail.com>
@AbrilRBS AbrilRBS self-assigned this Sep 2, 2023
@conan-center-bot conan-center-bot merged commit 15218ee into conan-io:master Sep 2, 2023
5 checks passed
ericLemanissier pushed a commit to ericLemanissier/conan-center-index that referenced this pull request Sep 15, 2023
* change conan v2 feedback message

Signed-off-by: Uilian Ries <uilianries@gmail.com>

* ping conan-io/barbarians

Signed-off-by: Uilian Ries <uilianries@gmail.com>

* Update .c3i/config_v2.yml

Co-authored-by: Daniel <danimanzaneque@gmail.com>

---------

Signed-off-by: Uilian Ries <uilianries@gmail.com>
Co-authored-by: Daniel <danimanzaneque@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants