You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d25b582
Browse filesBrowse the repository at this point in the historyBrowse files
[i18n] Update Tagalog code contributions guide to match English docs (#4354)
### Motivation for the change, related issues
English docs/main/contributing/code.md now uses Playground CLI for local
Multisite
([#3767](#3767))
and documents the Linux ENOSPC file watcher limit
([#3039](#3039)).
The Tagalog page still told contributors to run npx @wp-now/wp-now start
--port=80, omitted the Linux troubleshooting callout, and had no title
or description in the frontmatter. /tl/ readers would follow a CLI that
is no longer the documented local workflow.
### Implementation details
1. Updated
packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/contributing/code.md.
2. Added a Tagalog title and description in the frontmatter.
3. Replaced wp-now with Playground CLI, including npx
@wp-playground/cli@latest start --port=80.
4. Added the Linux file watcher troubleshooting callout (ENOSPC /
max_user_watches).
5. Matched the English git clone command block and restored the local
development tools link.
6. Kept the original English above each block in HTML comments, per the
translation guide.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Updated the Tagalog contribution guide with clearer page titles and
descriptions.
- Added a link to local development guidance.
- Improved setup instructions, including clearer repository cloning
steps.
- Added troubleshooting guidance for Linux file-watcher limit errors
(`ENOSPC`).
- Updated multisite instructions to use Playground CLI and its current
startup command.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
description: Gabay sa mga kontribusyon sa code, kabilang ang pag-fork ng repo, pag-set up ng lokal na environment, at pagsusumite ng pull request.
3
5
---
4
6
7
+
<!--
8
+
# Code contributions
9
+
-->
10
+
5
11
# Mga Kontribusyon sa Code
6
12
13
+
<!--
14
+
Like all WordPress projects, Playground uses GitHub to manage code and track issues. The main repository is at [https://github.com/WordPress/wordpress-playground](https://github.com/WordPress/wordpress-playground) and the Playground Tools repository is at [https://github.com/WordPress/playground-tools/](https://github.com/WordPress/playground-tools/).
15
+
-->
16
+
7
17
Tulad ng lahat ng WordPress projects, ginagamit ng Playground ang GitHub para pamahalaan ang code at subaybayan ang mga isyu. Ang pangunahing repositorya ay matatagpuan sa [https://github.com/WordPress/wordpress-playground](https://github.com/WordPress/wordpress-playground) at ang Playground Tools repositorya ay nasa [https://github.com/WordPress/playground-tools/](https://github.com/WordPress/playground-tools/).
8
18
19
+
<!--
20
+
<div class="callout callout-info">
21
+
22
+
**Contribute to Playground Tools**
23
+
24
+
This guide includes links to the main repository, but all the steps and options apply for both. If you're interested in the plugins or [local development](/developers/local-development/) tools—start there.
25
+
26
+
</div>
27
+
-->
28
+
9
29
<divclass="callout callout-info">
10
30
11
31
**Mag-ambag sa Playground Tools**
12
32
13
-
Kasama sa gabay na ito ang mga link sa pangunahing repositorya, ngunit ang lahat ng hakbang at opsyon ay magagamit din para sa Playground Tools. Kung interesado ka sa mga plugin o lokal na development tools—simulan mo doon.
33
+
Kasama sa gabay na ito ang mga link sa pangunahing repositorya, ngunit ang lahat ng hakbang at opsyon ay magagamit din para sa Playground Tools. Kung interesado ka sa mga plugin o [lokal na development](/developers/local-development/) tools—simulan mo doon.
14
34
15
35
</div>
16
36
37
+
<!--
38
+
Browse [the list of open issues](https://github.com/wordpress/wordpress-playground/issues) to find what to work on. The [`Good First Issue`](https://github.com/wordpress/wordpress-playground/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Issue%22) label is a recommended starting point for first-time contributors.
39
+
-->
40
+
17
41
I-browse ang [listahan ng mga bukas na isyu](https://github.com/wordpress/wordpress-playground/issues) upang makita kung saan ka maaaring magtrabaho. Ang label na [`Good First Issue`](https://github.com/wordpress/wordpress-playground/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Issue%22) ay inirerekomendang panimulang punto para sa mga unang beses na kontribyutor.
18
42
43
+
<!--
44
+
Be sure to review the following resources before you begin:
45
+
-->
46
+
19
47
Siguraduhing suriin ang mga sumusunod na resources bago ka magsimula:
-[Mga prinsipyo sa Coding](/contributing/coding-standards)
22
57
-[Arkitektura](/developers/architecture)
23
58
-[Bisyon at Pilosopiya](https://github.com/WordPress/wordpress-playground/issues/472)
24
59
-[Roadmap ng WordPress Playground](https://github.com/WordPress/wordpress-playground/issues/525)
25
60
61
+
<!--
62
+
## Contribute Pull Requests
63
+
-->
64
+
26
65
## Mag-ambag ng Pull Request
27
66
67
+
<!--
68
+
[Fork the Playground repository](https://github.com/WordPress/wordpress-playground/fork) and clone it to your local machine. To do that, copy and paste these commands into your terminal:
69
+
-->
70
+
28
71
[I-fork ang Playground repository](https://github.com/WordPress/wordpress-playground/fork) at i-clone ito sa iyong local machine. Upang gawin ito, kopyahin at i-paste ang mga utos na ito sa iyong terminal:
Create a branch, make changes, and test it locally by running the following command:
84
+
-->
85
+
36
86
Gumawa ng bagong branch, gumawa ng mga pagbabago, at i-test ito nang lokal sa pamamagitan ng pag-run ng sumusunod:
37
87
38
88
```bash
39
89
npm run dev
40
90
```
41
91
92
+
<!--
93
+
Playground will open in a new browser tab and refresh automatically with each change.
94
+
-->
95
+
42
96
Magbubukas ang Playground sa bagong browser tab at awtomatikong magre-refresh sa bawat pagbabago.
43
97
98
+
<!--
99
+
<div class="callout callout-tip">
100
+
101
+
**Troubleshooting: File watcher limit on Linux**
102
+
103
+
On Linux, you might see an error like `ENOSPC: System limit for number of file watchers reached` when running `npm run dev`. This happens because the Playground repository has more files than the default system limit allows to watch.
104
+
105
+
To fix this, first check your current limit:
106
+
107
+
```bash
108
+
cat /proc/sys/fs/inotify/max_user_watches
109
+
```
110
+
111
+
If it's around 65,536 or lower, increase it by running:
112
+
113
+
```bash
114
+
sudo sysctl fs.inotify.max_user_watches=131070
115
+
sudo sysctl -p
116
+
```
117
+
118
+
Then try `npm run dev` again. This is a common issue on Debian, Ubuntu, and other Linux distributions.
119
+
120
+
</div>
121
+
-->
122
+
123
+
<divclass="callout callout-tip">
124
+
125
+
**Troubleshooting: File watcher limit sa Linux**
126
+
127
+
Sa Linux, maaari kang makakita ng error tulad ng `ENOSPC: System limit for number of file watchers reached` kapag nagpapatakbo ng `npm run dev`. Nangyayari ito dahil mas maraming file ang Playground repository kaysa sa default na system limit para sa file watching.
128
+
129
+
Para ayusin ito, suriin muna ang kasalukuyang limit:
130
+
131
+
```bash
132
+
cat /proc/sys/fs/inotify/max_user_watches
133
+
```
134
+
135
+
Kung nasa 65,536 o mas mababa, taasan ito sa pamamagitan ng:
136
+
137
+
```bash
138
+
sudo sysctl fs.inotify.max_user_watches=131070
139
+
sudo sysctl -p
140
+
```
141
+
142
+
Pagkatapos, subukan ulit ang `npm run dev`. Karaniwan itong isyu sa Debian, Ubuntu, at iba pang Linux distribution.
143
+
144
+
</div>
145
+
146
+
<!--
147
+
When your'e ready, commit the changes and submit a Pull Request.
148
+
-->
149
+
44
150
Kapag handa ka na, i-commit ang mga pagbabago at mag-submit ng Pull Request.
45
151
152
+
<!--
153
+
<div class="callout callout-info">
154
+
155
+
**Formatting**
156
+
157
+
We handle code formatting and linting automatically. Relax, type away, and let the machines do the work.
158
+
159
+
</div>
160
+
-->
161
+
46
162
<divclass="callout callout-info">
47
163
48
164
**Pag-format**
@@ -51,33 +167,78 @@ Awtomatikong hinahandle ang code formatting at linting. Mag-relax ka lang, mag-t
51
167
52
168
</div>
53
169
170
+
<!--
171
+
### Running a local Multisite
172
+
-->
173
+
54
174
### Pagpapatakbo ng lokal na Multisite
55
175
56
-
May ilang [restriksyon kapag nagpapatakbo ng Multisite nang lokal](https://developer.wordpress.org/advanced-administration/multisite/prepare-network/#restrictions). Kung balak mong i-test ang Multisite network gamit ang `enableMultisite` step ng Playground, siguraduhing babaguhin mo ang default na port ng `wp-now` o mag-set ng lokal na test domain na tumatakbo sa HTTPS.
176
+
<!--
177
+
WordPress Multisite has a few [restrictions when run locally](https://developer.wordpress.org/advanced-administration/multisite/prepare-network/#restrictions). If you plan to test a Multisite network using Playground's `enableMultisite` step, make sure you either change Playground CLI's default port or set a local test domain running via HTTPS.
178
+
-->
57
179
58
-
Upang baguhin ang default na port ng `wp-now` sa suportadong port ng WordPress Multisite, patakbuhin ito gamit ang flag na `--port=80`:
180
+
May ilang [restriksyon kapag nagpapatakbo ng Multisite nang lokal](https://developer.wordpress.org/advanced-administration/multisite/prepare-network/#restrictions). Kung balak mong i-test ang Multisite network gamit ang `enableMultisite` step ng Playground, siguraduhing babaguhin mo ang default na port ng Playground CLI o mag-set ng lokal na test domain na tumatakbo sa HTTPS.
181
+
182
+
<!--
183
+
To change Playground CLI's default port to the one supported by WordPress Multisite, run it using the `--port=80` flag:
184
+
-->
185
+
186
+
Upang baguhin ang default na port ng Playground CLI sa suportadong port ng WordPress Multisite, patakbuhin ito gamit ang flag na `--port=80`:
59
187
60
188
```bash
61
-
npx @wp-now/wp-now start --port=80
189
+
npx @wp-playground/cli@latest start --port=80
62
190
```
63
191
192
+
<!--
193
+
There are a few ways to set up a local test domain, including editing your `hosts` file. If you're unsure how to do that, we suggest installing [Laravel Valet](https://laravel.com/docs/11.x/valet) and then running the following command:
194
+
-->
195
+
64
196
May ilang paraan upang mag-set up ng lokal na test domain, kabilang ang pag-edit ng iyong `hosts` file. Kung hindi ka sigurado kung paano gawin iyon, inirerekomenda naming i-install ang [Laravel Valet](https://laravel.com/docs/11.x/valet) at patakbuhin ang sumusunod:
65
197
66
198
```bash
67
199
valet proxy playground.test http://127.0.0.1:5400 --secure
68
200
```
69
201
202
+
<!--
203
+
Your dev server is now available on https://playground.test.
204
+
-->
205
+
70
206
Ngayon ay maa-access ang iyong dev server sa https://playground.test.
71
207
208
+
<!--
72
209
## Debugging
210
+
-->
211
+
212
+
## Debugging
213
+
214
+
<!--
215
+
### Use VS Code and Chrome
216
+
-->
73
217
74
218
### Paggamit ng VS Code at Chrome
75
219
220
+
<!--
221
+
If you're using VS Code and have Chrome installed, you can debug Playground in the code editor:
222
+
-->
223
+
76
224
Kung gumagamit ka ng VS Code at naka-install ang Chrome, maaari mong i-debug ang Playground sa code editor:
77
225
226
+
<!--
227
+
- Open the project folder in VS Code.
228
+
- Select Run > Start Debugging from the main menu or press `F5`/`fn`+`F5`.
229
+
-->
230
+
78
231
- Buksan ang project folder sa VS Code.
79
232
- Piliin ang Run > Start Debugging mula sa main menu o pindutin ang `F5`/`fn`+`F5`.
80
233
234
+
<!--
235
+
### Debugging PHP
236
+
-->
237
+
81
238
### Debugging PHP
82
239
240
+
<!--
241
+
Playground logs PHP errors in the browser console after every PHP request.
242
+
-->
243
+
83
244
Ina-log ng Playground ang PHP errors sa browser console pagkatapos ng bawat PHP request.
0 commit comments