Fix bunch of typos #36
Merged
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Oct 15, 2023 in 1s
1 rule matches and 3 potential rules
Rule: ci testing kalo sukses ke squash dengan label (merge)
-
check-success=golang_test
-
label=ready-to-merge
-
-conflict
[:pushpin: merge requirement] -
-draft
[:pushpin: merge requirement] -
-mergify-configuration-changed
[:pushpin: merge -> allow_merging_configuration_change setting requirement] -
base=main
Rule: ci testing kalo sukses ke squash dengan label (comment, label)
-
check-success=golang_test
-
label=ready-to-merge
-
base=main
Rule: golang label (label)
- any of:
-
body~=(?m)^\[X\] Saya membperbaiki algoritma yang sudah ada.
-
body~=(?m)^\[X\] Saya menambah algoritma terbaru.
-
files~=\.go$
-
Rule: markdown label (label)
- any of:
-
files~=\.md$
-
body~=(?m)^\[X\] Saya membperbaiki algoritma yang sudah ada.
-
body~=(?m)^\[X\] Saya menambah algoritma terbaru.
-
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branch
Additionally, on Mergify dashboard you can:
- look at your merge queues
- generate the Mergify configuration with the config editor.
Finally, you can contact us on https://mergify.com
Loading