Giter VIP home page Giter VIP logo

Comments (4)

njegosrailic avatar njegosrailic commented on May 23, 2024 1

It's not working properly. I'll take a look soon because I have introduced this issue.

from codeowners-validator.

mszostok avatar mszostok commented on May 23, 2024

the problem is that in current approach we are checking team permission entry which is out-dated

It no longer identifies thepermission a team has on its repos, but only specifies the default permission a repo is initially added with.

source: https://github.com/google/go-github/blob/6e0f6ebdef7d6db18d0eb92bb6f7aa9c0c7d4101/github/teams.go#L146-L151

what we need to do is to list the team repos and then check the permission:

func teamHasPermissions(team *github.Team, repoName string) (bool, error) {
	repos, _, err := ghClient.Teams.ListTeamRepos(ctx, team.GetID(), nil)
	if err != nil {
		return false, err
	}
	for _, r := range repos {
		if r.GetName() == repoName {
			var (
				perm     = r.GetPermissions()
				hasAdmin = containsPerm(perm, "admin")
				hasPush  = containsPerm(perm, "push")
			)
			return hasAdmin || hasPush, nil
		}
	}

	return false, nil
}

func containsPerm(perms map[string]bool, name string) bool {
	perm, _ := perms[name]
	return perm == true
}

other option is to use Review a user's permission level but it works currently only with users

from codeowners-validator.

mszostok avatar mszostok commented on May 23, 2024

Probably the best option is to use the GraphQL query to remove the overfetching problme, example query:

{
  organization(login: "gh-codeowners") {
    teams(first: 2) {
      pageInfo {
        hasNextPage
      }
      nodes {
        slug
        repositories(query: "codeowners-sample") {
          nodes {
            name
          }
          edges {
            permission
          }
        }
      }
    }
  }
}

can be used in https://developer.github.com/v4/explorer/

from codeowners-validator.

mszostok avatar mszostok commented on May 23, 2024

This issue was solved by #62. I do not close it because we can recheck if it is worth to change the implemented logic from REST to GraphQL.

More context: #62 (comment)

from codeowners-validator.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.