Anton Korobeynikov via llvm-dev
2021-Dec-29 07:24 UTC
[llvm-dev] Permission to work with GitHub issues
Well, GitHub is not quite flexible. The "triage" set of permissions is quite wide as it could also allow one to close issues & pull requests, etc. I will raise this question to IWG. On Wed, Dec 29, 2021 at 2:13 AM Eugene Zelenko via llvm-dev <llvm-dev at lists.llvm.org> wrote:> > Hi, Anton! > > I don't know how hard to implement this, but it may be reasonable to > make permission more gradual (for example, MediaWiki and WMF projects > have such setup), so simple issues modifications like tagging would > not require commit access. > > Eugene. > > On Tue, Dec 28, 2021 at 1:48 PM Anton Korobeynikov > <anton at korobeynikov.info> wrote: > > > > You do not have commit access to LLVM and therefore do not have write > > access to issues as well. The default role in the repo is read-only. > > > > On Tue, Dec 28, 2021 at 10:46 PM Eugene Zelenko via llvm-dev > > <llvm-dev at lists.llvm.org> wrote: > > > > > > Hi, David! > > > > > > According to my GitHub profile (https://github.com/EugeneZelenko) I > > > belong to LLVM organization. But it seems that it's not enough to be > > > able to add new labels to issues or close some of them (for example, > > > https://github.com/llvm/llvm-project/issues/39526). > > > > > > Eugene. > > > > > > On Tue, Dec 28, 2021 at 11:36 AM David Blaikie <dblaikie at gmail.com> wrote: > > > > > > > > I /think/ all it should take is being part of the LLVM project on github? But I'm not sure. I've seen some people having trouble closing bugs or the like - not sure of all the details/issues. > > > > > > > > On Tue, Dec 28, 2021 at 2:25 PM Eugene Zelenko via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > >> > > > >> Hi! > > > >> > > > >> What is procedure to get permissions to work with GitHub issues labels? > > > >> > > > >> I performed some kind of project management on Bugzilla reports > > > >> related to Clang-tidy in past and would like to do the same on GitHub. > > > >> > > > >> Eugene. > > > >> _______________________________________________ > > > >> LLVM Developers mailing list > > > >> llvm-dev at lists.llvm.org > > > >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > _______________________________________________ > > > LLVM Developers mailing list > > > llvm-dev at lists.llvm.org > > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > > > > > -- > > With best regards, Anton Korobeynikov > > Department of Statistical Modelling, Saint Petersburg State University > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University
Well, I have seen some open source projects use Github issue templates to automatically add labels and it don't need any permissions. Would it be a good choice? Eg: https://github.com/taichi-dev/taichi/ ---- 在 星期三, 29 十二月 2021 15:24:17 +0800 Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> 撰写 ---- Well, GitHub is not quite flexible. The "triage" set of permissions is quite wide as it could also allow one to close issues & pull requests, etc. I will raise this question to IWG. On Wed, Dec 29, 2021 at 2:13 AM Eugene Zelenko via llvm-dev <mailto:llvm-dev at lists.llvm.org> wrote:> > Hi, Anton! > > I don't know how hard to implement this, but it may be reasonable to > make permission more gradual (for example, MediaWiki and WMF projects > have such setup), so simple issues modifications like tagging would > not require commit access. > > Eugene. > > On Tue, Dec 28, 2021 at 1:48 PM Anton Korobeynikov > <mailto:anton at korobeynikov.info> wrote: > > > > You do not have commit access to LLVM and therefore do not have write > > access to issues as well. The default role in the repo is read-only. > > > > On Tue, Dec 28, 2021 at 10:46 PM Eugene Zelenko via llvm-dev > > <mailto:llvm-dev at lists.llvm.org> wrote: > > > > > > Hi, David! > > > > > > According to my GitHub profile (https://github.com/EugeneZelenko) I > > > belong to LLVM organization. But it seems that it's not enough to be > > > able to add new labels to issues or close some of them (for example, > > > https://github.com/llvm/llvm-project/issues/39526). > > > > > > Eugene. > > > > > > On Tue, Dec 28, 2021 at 11:36 AM David Blaikie <mailto:dblaikie at gmail.com> wrote: > > > > > > > > I /think/ all it should take is being part of the LLVM project on github? But I'm not sure. I've seen some people having trouble closing bugs or the like - not sure of all the details/issues. > > > > > > > > On Tue, Dec 28, 2021 at 2:25 PM Eugene Zelenko via llvm-dev <mailto:llvm-dev at lists.llvm.org> wrote: > > > >> > > > >> Hi! > > > >> > > > >> What is procedure to get permissions to work with GitHub issues labels? > > > >> > > > >> I performed some kind of project management on Bugzilla reports > > > >> related to Clang-tidy in past and would like to do the same on GitHub. > > > >> > > > >> Eugene. > > > >> _______________________________________________ > > > >> LLVM Developers mailing list > > > >> mailto:llvm-dev at lists.llvm.org > > > >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > _______________________________________________ > > > LLVM Developers mailing list > > > mailto:llvm-dev at lists.llvm.org > > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > > > > > -- > > With best regards, Anton Korobeynikov > > Department of Statistical Modelling, Saint Petersburg State University > _______________________________________________ > LLVM Developers mailing list > mailto:llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University _______________________________________________ LLVM Developers mailing list mailto:llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211229/fd0643b3/attachment.html>