Replies: 2 comments
-
I like it. ++ |
Beta Was this translation helpful? Give feedback.
-
Here is a current update, Props don't appear to make an entry within a user's profile. I'm told that Props are used to "add a BP contributor badge to the user’s profile" (see Slack message). However, if you read the entire message, there appears to be doubts as to whether Props should create an entry for BuddyPress, notwithstanding, there is an entry that is made for Core (see Slack message). What I find confusing, besides the Props process, is that the Meta Handbook indicates that the profile badge assignment for BuddyPress is a "Manual" process. After some additional probing, there is a class file Anyway, this is as far as I've gotten, thus far and dev-chat is about to start in roughly 20 minutes (July 10, 2024). I guess, the bottom line is that this appears to fall withing the jurisdiction of Meta. Edit: While waiting for dev-chat to start there was opportunity to observe whether a bbPress SVN commit with a Props line would add an entry for that user and it appears the Props line do not create an entry within a user's profile for bbPress, either. |
Beta Was this translation helpful? Give feedback.
-
This is primarily a segue of a conversation from Trac Ticket 9204 and a Slack message by @vapvarun regarding the WordPress props-bot-action for future use.
In short, I noticed that Props were not being recorded within WordPress User Profiles as related to BuddyPress activities. I found a page (Contributor Attribution (“Props”) that described the various aspects related to Props, in this case, specific to "How Props are given", in which there are 2 (two) methods:
I made a comment about item 1 (one) within Trac Ticket comment #10 and came to the conclusion that we should document a BuddyPress rendition of this page, once there is confirmation that the information related to commits to SVN is accurate; meaning confirmation is still pending.
Item 2 (two) is related to the aforementioned Slack message by @vapvarun and if there is a decision to use the action in the future, seems to me modifications are warranted, for example:
IIRC, there is also a comment about reviews and PRs from forked repos within the source code which is probably why the item 2 (two) information. The bottom line is that a ticket should be opened, if there is a decision to use the props-bot-action.
I guess 🤔 , now it's time to see if anyone is reading and, preferably, make comment. 😄
Beta Was this translation helpful? Give feedback.
All reactions