Replies: 1 comment 1 reply
-
Now I look more closely at the issues and pull requests, they are always "1". Even for "py2many" where I have 99 merged pulls. Also I have added However pywikibot is a less common case where there are no PRs - all dev is done in https://gerrit.wikimedia.org and a bot sync's commits to GitHub, so there wont be a event in my user push event stream, however the normal GitHub profile manages to display these events. A lot of larger orgs use this type of approach either because they dont like GitHub's workflow, or they don't trust the commercial GitHub as permanent archive and only use it as a secondary backup that is accessible to a wider audience. |
Beta Was this translation helpful? Give feedback.
-
For the notable plugin, I set
debug: true
andplugin_notable_types: commit, issue, pull_request
, and obviously haveindepth
enabled, and now I am seeing quite a few of the following in the logRun: https://github.com/jayvdb/jayvdb/runs/7468279468?check_suite_focus=true
I don't have any commits in that repo, but I did create an issue: https://github.com/pdm-project/pdm/issues/created_by/jayvdb
pdm now appears in my svg jayvdb/jayvdb@01ec971 without any of the numerical scores inside its circle.
So I am guessing that
plugin_notable_types
ofissue
&pull_request
are incompatible withindepth
at the moment, unless there was a commit also in the repo.But the problem is a bit more nuanced than that, as I only have a rejected issue in TheLartians/ModernCppStarter#131, and only an unmerged closed PR in ansible/ansible-lint#2196 - both repos that were "successfully processed".
Beta Was this translation helpful? Give feedback.
All reactions