-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch ci workflows #55
Conversation
🖕 #54 Signed-off-by: Fery Wardiyanto <[email protected]>
see https://github.com/shivammathur/setup-php/tree/v2/#github-composer-authentication Signed-off-by: Fery Wardiyanto <[email protected]>
Lha kampret, malah CI gak jalan? 🤦🏻♂️ Apa karna trigger hashtag : emosi |
as the name suggests this workflow meant to prepare all things needed for the next workflows. And in regards of workflow outputs please read more https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow Signed-off-by: Fery Wardiyanto <[email protected]>
Signed-off-by: Fery Wardiyanto <[email protected]>
read more about labeling https://github.com/actions/labeler Signed-off-by: Fery Wardiyanto <[email protected]>
Signed-off-by: Fery Wardiyanto <[email protected]>
Let's keep it bare minimum for now with exclution of all PRs by dependabot Signed-off-by: Fery Wardiyanto <[email protected]>
The main reason is by default auto release mechanism from github only gather information from pull request title and there's no way to have information regarding bug fixes, features and more importantly breaking changes (if any). The only way to get those info (at least for now) is only from commit so please make sure to make a commit message that informative enough so we could automate the rest. In this case is which commit message that tent to fix a bug, add features or breaking changes. Please read conventional commit for more info Signed-off-by: Fery Wardiyanto <[email protected]>
PR ini sebenernya agak merepotkan karna gak bisa langsung di check di PR, tapi perlu merge ke main dulu & bahkan bikin tag dulu untuk memastikan. Dan yang aku terapin disini hanya berdasarkan dokumentasi yang ada dari masing-masing tools. Jadi ya 🤞🏻 |
Apa benefit atau dalam hal apa kaitannya penggunaannya dari auto label pada setiap PR? |
Meminimalisir lupa assign label atau assign label yang kurang sesuai dengan scope pekerjaan nya. Dalam hal ini kebutuhan utamanya adalah untuk pembuatan release note. Walaupun aku rasa untuk saat ini masih belum optimal secara aturan, untuk itu aku harap ini jadi langkah awal untuk kita bisa mengoptimalkan mekanisme ini kedepannya. Belum lama ini aku nemu srvaroa/labeler yang memungkinkan kita gak cuma assign label tapi juga update PR title, contoh. Jadi release note nya gak perlu lagi ambil dari commit message kayak kita sekarang. |
PR ini ditujukan sebagai experiment untuk resolve #54, #36 dan #31
Target dari PR ini adalah :
actions/labeler