Talk pages project/Glossary

This page is intended to help us all communicate about talk pages more effectively by making sure we have shared understandings about the words we use in our discussions and documentation throughout the 1>Special:MyLanguage/Talk pages project|Talk Pages Project.

Miscellaneous
https://music.youtube.com/watch?v=5_eavxsSxkQ&feature=share Related resources • About regular expressions (opens in the Google Analytics Help Center) • google / RE2 / Syntax • Filter controls Give feedback about this article
 * Partner wikis - the Wikipedias we are partnering with to design and trial early versions of new talk page features. The four partner Wikipedias for the Reply tool project are: Arabic, Dutch, French and Hungarian.
 * Comments - the noun/object people use the Reply Tool to write and publish.

https://github.com/google/re2.wiki.git electron-upgrade-11.4.7 • What Is Npm? • What Is The Usage of Npm? • Components of npm • How to Install node? • Conclusion • NPM stands for Node Package Manager and is written in JavaScript that is considered to be the default package manager for Node.js. It was developed and maintained by Isaac Z. Schlueter on January 12, 2010. NPM helps manage all the Node.js packages, modules that come along with a command-line client called npm. Whenever you install Node.js, npm also gets installed with it. You can install the required packages and modules of Node.js using NPM. A package comes with all the files that are needed for a module. These modules are the JavaScript libraries that you can include in the Node.js project as per the project requirement. You can install NPM dependencies for a project using the package.json file. It allows you to update and uninstall NPM packages if no… Using the BFG The BFG Repo-Cleaner is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to git filter-branch for removing unwanted data. For example, to remove your file with sensitive data and leave your latest commit untouched, run:

$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA To replace all text listed in passwords.txt wherever it can be found in your repository's history, run:

$ bfg --replace-text passwords.txt After the sensitive data is removed, you must force push your changes to GitHub. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on. $ git push --force See the BFG Repo-Cleaner's documentation for full usage and download instructions. Using git filter-repo Warning: If you run git filter-repo after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running git filter-repo, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run git stash show -p | git apply -R. For more information, see Git Tools - Stashing and Cleaning.

To illustrate how git filter-repo works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to .gitignore to ensure that it is not accidentally re-committed.

• Install the latest release of the git filter-repo tool. You can install git-filter-repo manually or by using a package manager. For example, to install the tool with HomeBrew, use the brew install command.

brew install git-filter-repo For more information, see INSTALL.md in the newren/git-filter-repo repository.

• If you don't already have a local copy of your repository with sensitive data in its history, clone the repository to your local computer. $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ > remote: Counting objects: 1301, done. > remote: Compressing objects: 100% (769/769), done. > remote: Total 1301 (delta 724), reused 910 (delta 522) > Receiving objects: 100% (1301/1301), 164.39 KiB, done. > Resolving deltas: 100% (724/724), done.

• Navigate into the repository's working directory. $ cd YOUR-REPOSITORY

• Run the following command, replacing PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA with the path to the file you want to remove, not just its filename. These arguments will:

• Force Git to process, but not check out, the entire history of every branch and tag • Remove the specified file, as well as any empty commits generated as a result

• Remove some configurations, such as the remote URL, stored in the .git/config file. You may want to back up this file in advance for restoration later.

• Overwrite your existing tags$ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA Parsed 197 commits New history written in 0.11 seconds; now repacking/cleaning... Repacking your repo and cleaning out old unneeded objects Enumerating objects: 210, done. Counting objects: 100% (210/210), done. Delta compression using up to 12 threads Compressing objects: 100% (127/127), done. Writing objects: 100% (210/210), done. Building bitmaps: 100% (48/48), done. Total 210 (delta 98), reused 144 (delta 75), pack-reused 0 Completely finished after 0.64 seconds.This XML file does not appear to have any style information associated with it. The document tree is shown below.



https://en.wikipedia.org/w/api.php?action=feedcontributions&user=50.40.245.47&feedformat=atom

Wikipedia - User contributions [en]





2022-04-09T01:25:31Z

User contributions

MediaWiki 1.39.0-wmf.6

Related resources • About regular expressions (opens in the Google Analytics Help Center) • google / RE2 / Syntax • Filter controls Give feedback about this article

https://github.com/google/re2.wiki.git electron-upgrade-11.4.7 • What Is Npm? • What Is The Usage of Npm? • Components of npm • How to Install node? • Conclusion • NPM stands for Node Package Manager and is written in JavaScript that is considered to be the default package manager for Node.js. It was developed and maintained by Isaac Z. Schlueter on January 12, 2010. NPM helps manage all the Node.js packages, modules that come along with a command-line client called npm. Whenever you install Node.js, npm also gets installed with it. You can install the required packages and modules of Node.js using NPM. A package comes with all the files that are needed for a module. These modules are the JavaScript libraries that you can include in the Node.js project as per the project requirement. You can install NPM dependencies for a project using the package.json file. It allows you to update and uninstall NPM packages if no… Using the BFG The BFG Repo-Cleaner is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to git filter-branch for removing unwanted data. For example, to remove your file with sensitive data and leave your latest commit untouched, run:

$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA To replace all text listed in passwords.txt wherever it can be found in your repository's history, run:

$ bfg --replace-text passwords.txt After the sensitive data is removed, you must force push your changes to GitHub. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on. $ git push --force See the BFG Repo-Cleaner's documentation for full usage and download instructions. Using git filter-repo Warning: If you run git filter-repo after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running git filter-repo, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run git stash show -p | git apply -R. For more information, see Git Tools - Stashing and Cleaning.

To illustrate how git filter-repo works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to .gitignore to ensure that it is not accidentally re-committed.

• Install the latest release of the git filter-repo tool. You can install git-filter-repo manually or by using a package manager. For example, to install the tool with HomeBrew, use the brew install command.

brew install git-filter-repo For more information, see INSTALL.md in the newren/git-filter-repo repository.

• If you don't already have a local copy of your repository with sensitive data in its history, clone the repository to your local computer. $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ > remote: Counting objects: 1301, done. > remote: Compressing objects: 100% (769/769), done. > remote: Total 1301 (delta 724), reused 910 (delta 522) > Receiving objects: 100% (1301/1301), 164.39 KiB, done. > Resolving deltas: 100% (724/724), done.

• Navigate into the repository's working directory. $ cd YOUR-REPOSITORY

• Run the following command, replacing PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA with the path to the file you want to remove, not just its filename. These arguments will:

• Force Git to process, but not check out, the entire history of every branch and tag • Remove the specified file, as well as any empty commits generated as a result

• Remove some configurations, such as the remote URL, stored in the .git/config file. You may want to back up this file in advance for restoration later.

• Overwrite your existing tags$ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA Parsed 197 commits New history written in 0.11 seconds; now repacking/cleaning... Repacking your repo and cleaning out old unneeded objects Enumerating objects: 210, done. Counting objects: 100% (210/210), done. Delta compression using up to 12 threads Compressing objects: 100% (127/127), done. Writing objects: 100% (210/210), done. Building bitmaps: 100% (48/48), done. Total 210 (delta 98), reused 144 (delta 75), pack-reused 0 Completely finished after 0.64 seconds.File:File:Special:MyLanguage/1$ 174.250.210.245 M MediaWiki 1.39.0-wmf.6

Project key metrics

 * 1) Increase the number of Junior Contributors participating on talk pages
 * 2) Increase the short-term and long-term retention of Junior Contributors participating on talk pages.
 * 3) Increase the number of productive contributions to article pages made by Junior Contributors.

Key metric definitions

 * Junior Contributors: registered users who have made <100 cumulative contributions to a Wikipedia project.
 * Senior Contributors: registered users who have made >500 cumulative contributions to a Wikipedia project.
 * Participating on talk pages: successfully contributed to any of the 16 Wikipedia talk page namespaces that results in a diff that is not reverted
 * Talk pages: for the purposes of calculating our baseline metrics, we will include all 16 Wikipedia talk page namespaces.
 * Short-term retention: the percentage of contributors who make an edit to a talk page within 8 to 14 days of making their first edit to a talk page.
 * Long-term retention: the percentage of contributors who make an edit to a talk page within 15 to 30 days of making their first edit to a talk page.
 * Productive contributions to article pages: edits to Wikipedia articles that are not reverted.
 * Article pages: Namespace 0 or "Main/Article" namespace.
 * Contributions to Wikipedia: any action that results in a diff that is not reverted.
 * Contribution to talk pages: any action in any of the 16 Wikipedia talk page namespaces that results in a diff that is not reverted

For more information about these definitions, see this task where they were originally discussed: T234046