Welcome to the MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team!
The Meta team is responsible for maintaining and managing WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ websites. Our work is mostly done on the meta trac. If you see a bug, file a ticket!
From last Friday, WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles have started to show activity from the WordPress GitHubGitHubGitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ organization. This is shown when your WordPress.org & GitHub accounts are linked together. You can do this through your WordPress.org profile.
Currently we’re tracking New Issues submitted (by you), Closed Issues (by you), Pull requests submitted (by you), Pull requests merged (by you, and additionally the PR submitter gets a ‘PR Merged’ event), and finally Pushes to default branches.
There are a few limitations. We’re not currently accounting for PRs where commits are pushed to the PR by someone other than the submitter/merger. Similarly, if you push code from someone else then it may not be handled appropriately.
The code to display it on profiles.wordpress.org is unfortunately not yet open-sourced. It’s nothing overly special, but we realise this does limit the ability for submitting patches to that part of the code. MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets detailing a requested change including the Text/CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. required will be prioritised.
Most repositories activity items will display the team logo, but if it’s not known it’ll default to the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. code logo. If you find activity on a repository is tracked with the incorrect logo, create a meta ticket in the Profiles component or comment below.
Why doesn’t it list my Issues & Pull Requests?
That might be expected. We only have data for Friday onwards cached on WordPress.org. Importing all previous issues and pull requests is possible, an importer simply just hasn’t been written yet.
If you haven’t linked your GitHub account to WordPress.org, it won’t show then either. Good News! Once you link your account, it’ll show up immediately for any data that we have.
Some people who linked their GitHub account when that feature was first launched have since had their account link expire. This has since been fixed – they no longer expire. So if you thought you had linked it, but find it now not-linked, that’s likely why.
Are we showing too much information?
Should we combine events? For example; Today I submit a PR for review, later today I merge it, that’s two activity entries. Should it be merged together if within x hours? “Submitted & Merged PR #123 to WordPress/example-repo”
Are there any events you wish to see shown? Pull Request Reviews perhaps? Props for those who were commenters on the Issues/PRs?