Forbid using certain functions and classes #57738

anton-vlasenko · 2024-01-10T19:34:30Z

What?

This PR introduces the ForbiddenFunctionsAndClasses sniff.
It's designed to enforce usage restrictions on specific classes and functions within the Gutenberg project.
While declarations of these classes/functions are permitted, their actual usage is restricted based on defined regular expressions.

Fixes #54745.

Why?

The necessity of this PR arises from the need to avoid using any Gutenberg functions and classes in the block-library packages.
This is because these packages are backported to Core and must not include Gutenberg related functions and classes.

How?

The implementation involves defining regular expressions for restricted classes and functions.
The ForbiddenFunctionsAndClassesSniff class hooks into the PHP CodeSniffer process, scanning the code for instances where these restricted classes or functions are used.

Testing Instructions

Ensure that GitHub CI jobs pass.
Navigate to test/php/gutenberg-coding-standards/.
Run composer update.
Run composer run check-all.

Testing Instructions for Keyboard

Screenshots or screencast

github-actions · 2024-01-11T22:33:44Z

Flaky tests detected in 0c8ef69.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7717914499
📝 Reported issues:

[Flaky Test] callbacks should run whenever the specified event is dispatched #58398 in /test/e2e/specs/interactivity/directive-on-window.spec.ts
[Flaky Test] directives inside islands should not be hydrated twice #58332 in /test/e2e/specs/interactivity/tovdom-islands.spec.ts

anton-vlasenko · 2024-01-17T16:48:40Z

The PR fails CI checks because certain functions are not permitted within the block-library packages. Clarification is needed on whether to ignore or refactor these functions.

The list of problematic functions/classes:

FILE: /src/wp-content/plugins/gutenberg/packages/block-library/src/form/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 2 LINES
----------------------------------------------------------------------------------------------------------------------
49 | ERROR | It's not allowed to call the "gutenberg_is_experiment_enabled()" function as its name matches the
|       | forbidden pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
204 | ERROR | It's not allowed to call the "gutenberg_is_experiment_enabled()" function as its name matches the
|       | forbidden pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: /src/wp-content/plugins/gutenberg/packages/block-library/src/file/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
----------------------------------------------------------------------------------------------------------------------
25 | ERROR | It's not allowed to call the "gutenberg_enqueue_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
111 | ERROR | It's not allowed to call the "gutenberg_register_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
113 | ERROR | It's not allowed to call the "gutenberg_url()" function as its name matches the forbidden pattern:
|       | "/^(G|g)utenberg.*$/". (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: ...src/wp-content/plugins/gutenberg/packages/block-library/src/navigation/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
----------------------------------------------------------------------------------------------------------------------
341 | ERROR | It's not allowed to use the "Gutenberg_Navigation_Fallback" class as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.UsedClassInvalid)
431 | ERROR | It's not allowed to call the "gutenberg_register_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
433 | ERROR | It's not allowed to call the "gutenberg_url()" function as its name matches the forbidden pattern:
|       | "/^(G|g)utenberg.*$/". (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: /src/wp-content/plugins/gutenberg/packages/block-library/src/image/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
----------------------------------------------------------------------------------------------------------------------
55 | ERROR | It's not allowed to call the "gutenberg_enqueue_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
362 | ERROR | It's not allowed to call the "gutenberg_register_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
364 | ERROR | It's not allowed to call the "gutenberg_url()" function as its name matches the forbidden pattern:
|       | "/^(G|g)utenberg.*$/". (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: /src/wp-content/plugins/gutenberg/packages/block-library/src/search/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
----------------------------------------------------------------------------------------------------------------------
95 | ERROR | It's not allowed to call the "gutenberg_enqueue_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
217 | ERROR | It's not allowed to call the "gutenberg_register_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
219 | ERROR | It's not allowed to call the "gutenberg_url()" function as its name matches the forbidden pattern:
|       | "/^(G|g)utenberg.*$/". (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: ...src/wp-content/plugins/gutenberg/packages/block-library/src/form-input/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------------------------------------------------------
35 | ERROR | It's not allowed to call the "gutenberg_is_experiment_enabled()" function as its name matches the
|       | forbidden pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: /src/wp-content/plugins/gutenberg/packages/block-library/src/pattern/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------------------------------------------------------
61 | ERROR | It's not allowed to call the "gutenberg_serialize_blocks()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: /src/wp-content/plugins/gutenberg/packages/block-library/src/query/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 2 LINES
----------------------------------------------------------------------------------------------------------------------
73 | ERROR | It's not allowed to call the "gutenberg_enqueue_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
141 | ERROR | It's not allowed to call the "gutenberg_register_module()" function as its name matches the forbidden
|       | pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------


FILE: ...wordpress.test/src/wp-content/plugins/gutenberg/packages/block-library/src/form-submission-notification/index.php
----------------------------------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------------------------------------------------------
38 | ERROR | It's not allowed to call the "gutenberg_is_experiment_enabled()" function as its name matches the
|       | forbidden pattern: "/^(G|g)utenberg.*$/".
|       | (Gutenberg.CodeAnalysis.RestrictedFunctionsAndClasses.CalledFunctionInvalid)
----------------------------------------------------------------------------------------------------------------------

anton-vlasenko · 2024-01-17T20:10:46Z

I'd appreciate your feedback on that, @gziolo.
Should the sniff ignore these functions/classes? Or should they be removed from the block-library packages?
Also, any feedback on the sniff itself would be helpful.
Does it work as expected?
Is there anything that needs to be fixed, adjusted, or implemented? Thanks!

gziolo · 2024-01-22T06:47:43Z

I'd appreciate your feedback on that, @gziolo.
Should the sniff ignore #57738 (comment) functions/classes? Or should they be removed from the block-library packages?

The sniff works great detecting all listed violations 👍

Some of these code paths are behind the check ensuring they only execute in the Gutenberg context so folks can explicitly disable violations for these lines.

It looks like other calls will fail in WordPress core like these unconditionally calling gutenberg_is_experiment_enabled(). This is where the sniff is the most helpful.

Overall, I find this new rule very helpful as it will remind folks to default to syntax available in WordPress core.

anton-vlasenko · 2024-01-26T14:43:12Z

@gziolo I really appreciate your feedback.
I've improved the sniff, so now it can detect whether a function/class is guarded (i.e., being called in the Gutenberg context) and not throw errors.
Also, to make the PR pass CI checks, I've added temporary //phpcs:ignore statements (please see ef5388f).

An example of such statement would be:

// Refactoring required: this function must be guarded as it is available only in Gutenberg, not in Core.

I plan to create another GitHub issue specifically to address the refactoring of these occurrences after this PR is merged.

If the PR looks good to you, both in terms of code and functionality, may I ask for your approval? 🙏

azaozz · 2024-01-26T21:36:13Z

packages/block-library/src/file/index.php

 	wp_register_script_module(
 		'@wordpress/block-library/file',
-		defined( 'IS_GUTENBERG_PLUGIN' ) && IS_GUTENBERG_PLUGIN ? gutenberg_url( '/build/interactivity/file.min.js' ) : includes_url( 'blocks/file/view.min.js' ),
+		$module_url ?? includes_url( 'blocks/file/view.min.js' ),


Seems this should work in PHP 7.0+. Just unsure if Gutenberg still has to support 5.6?

7 or higher according to the plugin directory. There's a whole discussion around whether WP "officially" supports the null coalescing operator or not but I think at this point we should be fine to start using it 😅

You can always initialize the $module_url before IS_GUTENBERG_PLUGIN check to avoid the conditional here.

7 or higher according to the plugin directory. There's a whole discussion around whether WP "officially" supports the null coalescing operator or not but I think at this point we should be fine to start using it 😅

The null coalescing operator has not yet been accepted into the WordPress Coding Standards. There is a Trac ticket open for it.

Until this ticket or a proposal for it (and other PHP 7.0 syntax) is accepted into Core, please don't use it (yet) for code that will be merged into Core. Why? It will be get removed once it comes to Core.

So to ease the sync process between GB and Core, I'd advise to not use it yet.

I thought the null coalescing operator was OK to use in Gutenberg considering its extensive usage throughout the Gutenberg codebase: https://github.com/search?q=repo%3AWordPress%2Fgutenberg+path%3A*.php+language%3APHP+%3F%3F&type=code&ref=advsearch.
But I didn't check if it's actually allowed.
I agree with @hellofromtonya, let's not use ?? until it's officially accepted in Core (and appreciate the link to the Trac discussion).
Fixed in 1b61304a422ff9d8bd1f1bbdf30215f3b1ff75ce.

You can always initialize the $module_url before IS_GUTENBERG_PLUGIN check to avoid the conditional here.

I didn't want to initialize it before the IS_GUTENBERG_PLUGIN check for performance-related reasons. But yes, that was an option.

tellthemachines

Thanks for the PR, this is looking pretty good! I think we should try and merge this, see how it works and then iterate if needed. Also it looks like most of the refactoring to be done is in experimental blocks that aren't going into 6.5 so our codebase seems to be in a good place overall 😄

tellthemachines · 2024-01-29T04:23:06Z

...tenberg-coding-standards/Gutenberg/Sniffs/CodeAnalysis/ForbiddenFunctionsAndClassesSniff.php

+		$conditions = array_reverse( $tokens[ $stack_pointer ]['conditions'], true );
+
+		// Matches the "if ( defined( 'IS_GUTENBERG_PLUGIN' ) && IS_GUTENBERG_PLUGIN" string.
+		$regexp = '/if\s*\(\s*defined\(\s*(\'|")IS_GUTENBERG_PLUGIN(\'|")\s*\)\s*&&\s*IS_GUTENBERG_PLUGIN/';


I'm wondering if there would ever be a reason to make this check configurable? Checking for IS_GUTENBERG_PLUGIN makes sense in block_library or any other PHP files that may be auto-generated in core from the npm packages. I guess this kind of logic wouldn't be needed at all if we were using the sniff in plugin-specific PHP files.

The sniff is currently only checking the /packages/block-library folder: https://github.com/WordPress/gutenberg/pull/57738/files#diff-05ae9cddcaec1e845771a7db224961439f83ef5939ec67d3a48744cb34d7e58bR157
So, it doesn't check files in other folders.
I hope I've understood your question correctly.

gziolo · 2024-01-29T07:45:22Z

packages/block-library/src/navigation/index.php

@@ -980,6 +980,8 @@ function block_core_navigation_get_fallback_blocks() {
 	if ( class_exists( 'WP_Navigation_Fallback' ) ) {
 		$navigation_post = WP_Navigation_Fallback::get_fallback();
 	} else {
+		// Refactoring required: this class must be guarded as it is available only in Gutenberg, and not in Core.
+		// phpcs:ignore Gutenberg.CodeAnalysis.ForbiddenFunctionsAndClasses.ForbiddenClassUsage


This is the only file that has the phpcs:ignore comment included that is going to sync to WP core. Will it work correctly without the rule defined? I simply don't know how PHPCS works so the answer will be simple.

It will not generate any errors if the ignored rule is not defined.
However, I've moved these to the phpcs.xml.dist file in 255e3ed to avoid cluttering the code with phpcs:ignore statements. I hope that these files will be refactored soon, allowing for the removal of the exclude-pattern statements.

gziolo · 2024-01-29T07:49:15Z

phpcs.xml.dist

+				<element value="(G|g)utenberg.*"/>
+			</property>
+			<property name="forbidden_classes" type="array">
+				<element value="(G|g)utenberg.*"/>


Nit: technically speaking, it should be enough to use the following:

Suggested change

<element value="(G|g)utenberg.*"/>

</property>

<property name="forbidden_classes" type="array">

<element value="(G|g)utenberg.*"/>

<element value="gutenberg.*"/>

</property>

<property name="forbidden_classes" type="array">

<element value="Gutenberg.*"/>

Although, maybe I'm missing some special cases.

You are right.
However, to be on the safer side, I would prefer to allow the first letter to be either 'G' or 'g'.
it's just my personal preference.

gziolo

This is a great start. I left a couple of nitpicks to consider, but none of them are blockers. This should be a big help for the Gutenberg syncing in WordPress Core, as so far it's been always on the editor release leads to catch these code paths.

@youknowriad and @getdave, anything we could miss based on the experience in the WP 6.5 release so far?

youknowriad · 2024-01-29T08:26:38Z

Great work here 👍 This is going to help us a lot.

getdave · 2024-01-29T10:11:12Z

packages/block-library/src/navigation/index.php

+		// Refactoring required: this class must be guarded as it is available only in Gutenberg, and not in Core.
+		// phpcs:ignore Gutenberg.CodeAnalysis.ForbiddenFunctionsAndClasses.ForbiddenClassUsage


@tjcafferkey @ockham Did we introduce the called to the Gutenberg_ prefixed version of this class in the recent work on hooks in the Nav block?

I'm removing this in #58369 I don't see where this class is defined at all.

getdave

Great work. This will make a big difference. Merge and iterate 👍

Would it help if someone (me?) made an Issue to track resolving the outstanding cases you've had to ignore here? Would be good to get these resolved.

…f this sniff.

…f functions/classes.

…void cluttering the code with `phpcs:ignore` statements.

anton-vlasenko · 2024-01-30T23:08:01Z

Great work. This will make a big difference. Merge and iterate 👍

Would it help if someone (me?) made an Issue to track resolving the outstanding cases you've had to ignore here? Would be good to get these resolved.

@getdave Awesome. Yes, please go ahead and create a GitHub issue to track resolving the outstanding cases.
FYI, I've moved the ignore statements to the phpcs.xml.dist file in 255e3ed.

anton-vlasenko · 2024-01-31T13:19:42Z

Thank you all!

anton-vlasenko added the [Type] Code Quality Issues or PRs that relate to code quality label Jan 10, 2024

anton-vlasenko marked this pull request as ready for review January 17, 2024 16:42

anton-vlasenko requested review from gziolo, tellthemachines and ironprogrammer January 17, 2024 20:10

anton-vlasenko requested review from artemiomorales, michalczaplinski and ajitbohra as code owners January 23, 2024 23:41

anton-vlasenko force-pushed the try/forbid-calling-disallowed-functions-sniff branch 2 times, most recently from f032c82 to 0277771 Compare January 25, 2024 19:30

anton-vlasenko requested review from hellofromtonya and azaozz January 26, 2024 14:47

azaozz reviewed Jan 26, 2024

View reviewed changes

tellthemachines approved these changes Jan 29, 2024

View reviewed changes

gziolo reviewed Jan 29, 2024

View reviewed changes

gziolo approved these changes Jan 29, 2024

View reviewed changes

getdave reviewed Jan 29, 2024

View reviewed changes

getdave assigned anton-vlasenko Jan 29, 2024

getdave approved these changes Jan 29, 2024

View reviewed changes

anton-vlasenko force-pushed the try/forbid-calling-disallowed-functions-sniff branch from d185d8f to 1b61304 Compare January 30, 2024 18:16

anton-vlasenko added 3 commits January 30, 2024 20:52

Add a new property to the PHPCS sniff.

0005ff9

Commit WIP.

7d473cd

Commit WIP.

efa3918

anton-vlasenko added 22 commits January 30, 2024 20:52

Fix the sniff.

5a0a63d

Fix the config.

8e64c08

Remove redundnat code.

3dbd5a8

Refactor the sniff, add descriptions.

66cc48f

Fix doc blocks.

b8e4742

Implement the test for the RestrictedFunctionsAndClassesSniff sniff.

dde1e6d

Implement the test for the RestrictedFunctionsAndClassesSniff sniff.

5d9b80e

Rename Restricted to Forbidden as forbidden is a better description o…

f1cf5bd

…f this sniff.

Rename properties.

f10aee5

Rename properties.

9ff2764

Fix typo.

829310d

Change error codes.

1047a39

Teach the sniff not to flag guarded and, therefore, legitimate uses o…

c0437fc

…f functions/classes.

Improve checks for guarded functions/classes.

4cd7b18

Better explanation + fix code style.

539406c

Add phpcs:ignore statements.

9b590f8

Refactor the code so that the sniff doesn't flag it.

c1ebd27

Fix typo.

6bfd934

Fix code style.

588a094

Fix typo.

9cd966d

Add unit tests.

ae6a161

Fallback to isset().

8249699

anton-vlasenko force-pushed the try/forbid-calling-disallowed-functions-sniff branch from 1b61304 to 8249699 Compare January 30, 2024 19:54

anton-vlasenko added 2 commits January 30, 2024 22:51

Improve the regular expression.

0c8ef69

Move the exclude pattern statements to the phpcs.xml.dist file to a…

255e3ed

…void cluttering the code with `phpcs:ignore` statements.

anton-vlasenko merged commit 7fd9023 into trunk Jan 31, 2024
55 checks passed

anton-vlasenko deleted the try/forbid-calling-disallowed-functions-sniff branch January 31, 2024 13:19

t-hamano mentioned this pull request Jul 3, 2024

Button Block: Add back compat for WP6.4 regarding HTML Tag Processor #63082

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Forbid using certain functions and classes #57738

Forbid using certain functions and classes #57738

anton-vlasenko commented Jan 10, 2024 •

edited

Loading

github-actions bot commented Jan 11, 2024 •

edited

Loading

anton-vlasenko commented Jan 17, 2024 •

edited

Loading

anton-vlasenko commented Jan 17, 2024 •

edited

Loading

gziolo commented Jan 22, 2024

anton-vlasenko commented Jan 26, 2024 •

edited

Loading

azaozz Jan 26, 2024 •

edited

Loading

tellthemachines Jan 29, 2024

gziolo Jan 29, 2024

hellofromtonya Jan 29, 2024

anton-vlasenko Jan 30, 2024 •

edited

Loading

anton-vlasenko Jan 30, 2024

tellthemachines left a comment

tellthemachines Jan 29, 2024

anton-vlasenko Jan 30, 2024

gziolo Jan 29, 2024 •

edited

Loading

anton-vlasenko Jan 30, 2024

gziolo Jan 29, 2024

anton-vlasenko Jan 30, 2024

gziolo left a comment

youknowriad commented Jan 29, 2024

getdave Jan 29, 2024

youknowriad Jan 29, 2024

getdave left a comment

anton-vlasenko commented Jan 30, 2024

anton-vlasenko commented Jan 31, 2024 •

edited

Loading

		// Refactoring required: this class must be guarded as it is available only in Gutenberg, and not in Core.
		// phpcs:ignore Gutenberg.CodeAnalysis.ForbiddenFunctionsAndClasses.ForbiddenClassUsage

Forbid using certain functions and classes #57738

Forbid using certain functions and classes #57738

Conversation

anton-vlasenko commented Jan 10, 2024 • edited Loading

What?

Why?

How?

Testing Instructions

Testing Instructions for Keyboard

Screenshots or screencast

github-actions bot commented Jan 11, 2024 • edited Loading

anton-vlasenko commented Jan 17, 2024 • edited Loading

anton-vlasenko commented Jan 17, 2024 • edited Loading

gziolo commented Jan 22, 2024

anton-vlasenko commented Jan 26, 2024 • edited Loading

azaozz Jan 26, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

anton-vlasenko Jan 30, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tellthemachines left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gziolo Jan 29, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gziolo left a comment

Choose a reason for hiding this comment

youknowriad commented Jan 29, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

getdave left a comment

Choose a reason for hiding this comment

anton-vlasenko commented Jan 30, 2024

anton-vlasenko commented Jan 31, 2024 • edited Loading

anton-vlasenko commented Jan 10, 2024 •

edited

Loading

github-actions bot commented Jan 11, 2024 •

edited

Loading

anton-vlasenko commented Jan 17, 2024 •

edited

Loading

anton-vlasenko commented Jan 17, 2024 •

edited

Loading

anton-vlasenko commented Jan 26, 2024 •

edited

Loading

azaozz Jan 26, 2024 •

edited

Loading

anton-vlasenko Jan 30, 2024 •

edited

Loading

gziolo Jan 29, 2024 •

edited

Loading

anton-vlasenko commented Jan 31, 2024 •

edited

Loading