Skip to content

add codeowner to inc_nlohmann_json#93

Merged
kairoaraujo merged 6 commits intoeclipse-score:mainfrom
score-json:erikhu1-add_inc_nlohmann_json_codeowners
Nov 7, 2025
Merged

add codeowner to inc_nlohmann_json#93
kairoaraujo merged 6 commits intoeclipse-score:mainfrom
score-json:erikhu1-add_inc_nlohmann_json_codeowners

Conversation

@Erikhu1
Copy link
Contributor

@Erikhu1 Erikhu1 commented Oct 29, 2025

Adding @4og as codeowner and bypass actor to inc_nlohmann_json

@Erikhu1 Erikhu1 requested a review from a team as a code owner October 29, 2025 14:06
@eclipse-otterdog
Copy link
Contributor

Thank you for raising a pull request to update the configuration of your GitHub organization.
You can manually add reviewers to this PR to eventually enable auto-merging.

The following conditions need to fulfilled for auto-merging to be available:

  • valid configuration
  • approved by a project lead
  • does not require any secrets
  • does not update settings only accessible via the GitHub Web UI
  • does not remove any resource
Otterdog commands and options

You can trigger otterdog actions by commenting on this PR:

  • /otterdog team-info checks the team / org membership for the PR author
  • /otterdog validate validates the configuration change
  • /otterdog validate info validates the configuration change, printing also validation infos
  • /otterdog check-sync checks if the base ref is in sync with live settings
  • /otterdog merge merges and applies the changes if the PR is eligible for auto-merging (only accessible for the author)
  • /otterdog done notifies the self-service bot that a required manual apply operation has been performed (only accessible for members of the admin team)
  • /otterdog apply re-apply a previously failed attempt (only accessible for members of the admin team)

@eclipse-otterdog
Copy link
Contributor

The author (Erikhu1) of this PR is associated with this organization in the role of MEMBER.

Additionally, Erikhu1 is a member of the following teams:

@eclipse-otterdog

This comment has been minimized.

@eclipse-otterdog

This comment has been minimized.

@eclipse-otterdog

This comment has been minimized.

@kairoaraujo
Copy link
Contributor

cc @eclipse-score/automotive-score-project-leads @eclipse-score/automotive-score-committers

Copy link
Contributor

@FScholPer FScholPer left a comment

Choose a reason for hiding this comment

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

Please

"refs/heads/main"
],
required_pull_request+: default_review_rule,
bypass_actors+: [
Copy link
Contributor

Choose a reason for hiding this comment

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

Please use codeowner files

Copy link
Contributor Author

@Erikhu1 Erikhu1 Nov 3, 2025

Choose a reason for hiding this comment

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

Sorry, could you please elaborate? I should update the codeowner file in https://github.com/eclipse-score/inc_nlohmann_json first ?

Copy link
Member

Choose a reason for hiding this comment

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

Do you really need bypass_actors? Or is CODEOWNERS sufficient?

Copy link
Contributor Author

@Erikhu1 Erikhu1 Nov 3, 2025

Choose a reason for hiding this comment

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

For the migration of the TSF documentation for the json parsing library from https://github.com/score-json/json into https://github.com/eclipse-score/inc_nlohmann_json, we need someone (for example @4og) who can create a main branch in the target repo with some specific content.

To do that, they need to be able to bypass the default review ruleset for main branch (see https://otterdog.eclipse.org/projects/automotive.score/repos/inc_nlohmann_json#rulesets). Currently, trying to create a main branch leads to "error: GH013: Repository rule violations found for refs/heads/main".

I assume CODEOWNERS is not sufficient to bypass the default review ruleset for main, or?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just tested the above by adding the user to CODEOWNERS file: eclipse-score/nlohmann_json#1

Was not sufficient unfortunately.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No. The develop branch is also needed for the migration. We want to create a new main branch from https://github.com/nlohmann/json/releases/tag/v3.12.0, and then set the main branch as the default.

Copy link
Contributor

Choose a reason for hiding this comment

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

That means everytime a new tag is created you want to switch the main to a new tag?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

New releases would be introduced into develop, then merged to main via PR. No "switching" or bypassing of the ruleset in main will be needed after completing the migration.

Copy link
Contributor

Choose a reason for hiding this comment

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

  • Okay then I would say for one timer its okay. Then please
  1. Migrate and create a new pull request to remove the bypassing
  2. Add more committer to the codeowner file (at least two) as maintainers

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Understood, will do. Thanks a lot!

@eclipse-otterdog

This comment has been minimized.

@eclipse-otterdog

This comment has been minimized.

@eclipse-otterdog

This comment has been minimized.

@Erikhu1
Copy link
Contributor Author

Erikhu1 commented Nov 4, 2025

cc @eclipse-score/automotive-score-project-leads @eclipse-score/automotive-score-committers

Can this be merged please?

@Erikhu1 Erikhu1 requested a review from FScholPer November 4, 2025 14:18
@eclipse-otterdog
Copy link
Contributor

Please find below the validation of the requested configuration changes:

Diff for 082dd6e
Project automotive.score[github_id=eclipse-score]
  there have been 25 validation infos, enable verbose output to display them.

+  add team[name="codeowner-inc_nlohmann_json"] {
+    description                   = ""
+    members                       = [
+      "4og"
+    ],
+    name                          = "codeowner-inc_nlohmann_json"
+    notifications                 = true
+    privacy                       = "visible"
+    skip_members                  = false
+    skip_non_organization_members = true
+  }

  
!   repo_ruleset[name="main", repository=inc_nlohmann_json] {
!     bypass_actors           = [
+      "@eclipse-score/codeowner-inc_nlohmann_json"
!     ]
!     requires_linear_history = false -> true
!   }
  
  Plan: 1 to add, 2 to change, 0 to delete.

@eclipse-otterdog
Copy link
Contributor

Warning

The current configuration is out-of-sync with the live settings:

Diff to live settings
Project automotive.score[github_id=eclipse-score]
  there have been 25 validation infos, enable verbose output to display them.

  
!   team[name="cft-orchestration"] {
!     members = [
+      "pawelrutkaq"
+      "vinodreddy-g"
!     ]
!   }

  
!   team[name="cft-persistency"] {
!     members = [
+      "arkjedrz"
+      "vinodreddy-g"
!     ]
!   }

  
!   repository[name="reference_integration"] {
!     code_scanning_default_languages = [
-      "actions"
!     ]
!   }
  
  Plan: 0 to add, 3 to change, 0 to delete.

Important

The current configuration needs to be updated to reflect the live settings otherwise they would be overwritten when this PR gets merged.

cc @eclipse-score/eclipsefdn-security

cc @eclipse-score/eclipsefdn-releng

@Erikhu1
Copy link
Contributor Author

Erikhu1 commented Nov 7, 2025

cc @eclipse-score/automotive-score-project-leads @eclipse-score/automotive-score-committers

Can this be merged please?

^

@thilo-schmitt
Copy link

/otterdog merge

@FScholPer
Copy link
Contributor

@kairoaraujo can you please check the sync?

@kairoaraujo kairoaraujo merged commit ed3ae02 into eclipse-score:main Nov 7, 2025
3 checks passed
@eclipse-otterdog
Copy link
Contributor

Caution

The changes could not be applied successfully, please check the output:

Project automotive.score[github_id=eclipse-score]
  there have been 25 validation infos, enable verbose output to display them.

+  add team[name="codeowner-inc_nlohmann_json"] {
+    description                   = ""
+    members                       = [
+      "4og"
+    ],
+    name                          = "codeowner-inc_nlohmann_json"
+    notifications                 = true
+    privacy                       = "visible"
+    skip_members                  = false
+    skip_non_organization_members = true
+  }

  
!   repo_ruleset[name="main", repository=inc_nlohmann_json] {
!     bypass_actors           = [
+      "@eclipse-score/codeowner-inc_nlohmann_json"
!     ]
!     requires_linear_history = false -> true
!   }

  
  Applying changes:

-                                                                                                             
- Error:   failed to apply patch: ADD- team[name="codeowner-inc_nlohmann_json"]                              
-          failed to add team 'codeowner-inc_nlohmann_json': {"message":"Resource not accessible by           
-          integration","documentation_url":"https://docs.github.com/rest/teams/teams#create-a-team","statu…  
-                                                                                                             

-                                                                                                             
- Error:   failed to apply patch: CHANGE- repo_ruleset[name="main", repository=inc_nlohmann_json]            
-          failed retrieving team node id:                                                                    
-          Exception while accessing                                                                          
-          'http://ghproxy:8888/orgs/eclipse-score/teams/codeowner-inc_nlohmann_json': (status=404,           
-          body={"message":"Not                                                                               
-          Found","documentation_url":"https://docs.github.com/rest/teams/teams#get-a-team-by-name","status…  
-                                                                                                             
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00
  
  Done.
  
  Executed plan: 1 added, 2 changed, 0 deleted.

cc @eclipse-score/eclipsefdn-security

cc @eclipse-score/eclipsefdn-releng

@4og
Copy link
Member

4og commented Nov 8, 2025

@kairoaraujo, based on the error above, it looks like it didn't work. Can you please check?

I'm still getting the rule violation issue when trying to push to inc_nlohmann_json main branch.

@Erikhu1
Copy link
Contributor Author

Erikhu1 commented Nov 11, 2025

@eclipse-score/automotive-score-project-leads @eclipse-score/automotive-score-committers @kairoaraujo
Can someone please have a look at the above?

@kairoaraujo
Copy link
Contributor

Fixed
/otterdog done

@kairoaraujo
Copy link
Contributor

/otterdog done

@eclipse-otterdog
Copy link
Contributor

Note

The PR has been marked as being completed.

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.

6 participants