Replies: 3 comments 2 replies
-
另外,目前github reaction 只有8种
|
Beta Was this translation helpful? Give feedback.
1 reply
-
有时候解决问题需要去仓库的issue里找,这个时候最多的“+1”在一大片comment中闪闪发光,一下子就能找到问题的解决方法。如果这个方法的确可行,我也会点一下“+1”,于是我也算成为了一个参与者。 |
Beta Was this translation helpful? Give feedback.
1 reply
-
挖一下坟: {
repository(owner: "X-lab2017", name: "open-digger") {
issues(last: 10) {
nodes {
title
reactions(first: 10) {
nodes {
content
user {
login
}
createdAt
}
}
}
}
}
} 我做了一点graphql的尝试只是获得issue原文的互动表情,也可以获得获得comments的reaction不过太长了。总的来说感觉graphql功能的局限性也有的,因为语法不提供真正的聚合,所以比较依赖其他语言或者工具去聚合,或者祈祷他们服务端直接提供聚合的字段(目前看起来是是只有按照reaction种类的聚合)。 要获得reaction的话,得从issue和pr的正文+所有的comments来获取了,查出来的json会非常长,这个接口的限制是50000,所以挺难受的,不过据说也有一个idl的接口提供压缩的结果。 {
"data": {
"repository": {
"issues": {
"nodes": [
{
"title": "[Label Data] Add new org (1Panel-dev) to FIT2CLOUD",
"reactions": {
"nodes": []
}
},
{
"title": "[Bug] Data information is missing for a month of the project",
"reactions": {
"nodes": []
}
},
{
"title": "OpenDigger Biweekly Meeting: 2023-03-22",
"reactions": {
"nodes": [
{
"content": "THUMBS_UP",
"user": {
"login": "xgdyp"
},
"createdAt": "2023-03-28T01:23:54Z"
}
]
}
},
{
"title": "OpenDigger Biweekly Meetings, 2023",
"reactions": {
"nodes": [
{
"content": "THUMBS_UP",
"user": {
"login": "tyn1998"
},
"createdAt": "2023-03-22T15:49:44Z"
},
{
"content": "ROCKET",
"user": {
"login": "tyn1998"
},
"createdAt": "2023-03-22T15:49:47Z"
}
]
}
},
{
"title": "[WeeklyReport] Weekly report for open-digger 3/20/2023 to 3/27/2023",
"reactions": {
"nodes": []
}
},
{
"title": "[Question] The scope of the actor metrics",
"reactions": {
"nodes": [
{
"content": "EYES",
"user": {
"login": "Zzzzzhuzhiwei"
},
"createdAt": "2023-03-29T10:20:09Z"
}
]
}
},
{
"title": "[Batch Label Data] Add more label data for Database technical area labled on dbdb.io and DB-Engines Ranking by Mar 31st, 2023.",
"reactions": {
"nodes": []
}
},
{
"title": "[OSPP2023] Idea list for Summer 2023",
"reactions": {
"nodes": [
{
"content": "THUMBS_UP",
"user": {
"login": "tyn1998"
},
"createdAt": "2023-04-05T05:28:04Z"
},
{
"content": "ROCKET",
"user": {
"login": "tyn1998"
},
"createdAt": "2023-04-05T05:28:07Z"
}
]
}
},
{
"title": "OpenDigger Biweekly Meeting: 2023-04-05",
"reactions": {
"nodes": [
{
"content": "THUMBS_UP",
"user": {
"login": "tyn1998"
},
"createdAt": "2023-04-05T06:35:14Z"
},
{
"content": "ROCKET",
"user": {
"login": "shinyzhu"
},
"createdAt": "2023-04-05T14:27:37Z"
}
]
}
},
{
"title": "[potential label data] Generative AI OSS",
"reactions": {
"nodes": [
{
"content": "THUMBS_UP",
"user": {
"login": "frank-zsy"
},
"createdAt": "2023-04-06T13:31:26Z"
}
]
}
}
]
}
}
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
在2016年,GitHub上线了reaction机制,几年下来,reaction emoji已经成为了GitHub社交活动中重要的一部分。
其实,像Slack, Facebook, Pokemon, Youtube都有类似的机制。那么现在就有个问题,这种机制到底起到了什么作用呢?
通过查阅资料和讨论,我们得到了三个点:
一篇论文:More Than React: Investigating The Role of EmojiReaction in GitHub Pull Requests 讨论了相关的机制
他主要讨论了四个问题 分别是:
我自己觉得其实好像还有别的问题可以再探讨,因此就先抛砖引玉,希望大家能多讨论讨论
我觉得可以讨论的问题包括:
为探索这些问题,我简单的写了一个小工具可以获得指定仓库的reaction数据
目前的进度:
下面展示下我们org下面的几个repo的issue+pr reaction数据
DesignThinking-LeanStartup
open-research
open-digger
open-wonderland
大家对于reaction机制有什么想法欢迎讨论,看到这个discussion不妨点个reaction~
Beta Was this translation helpful? Give feedback.
All reactions