Confirm deletion of blog #602

マージ済み

rfwatson が 1 個のコミットを feature/confirm_delete_blog から master へマージ

rfwatson がコメント (github.comから移行)

Closes #601.

~Ideally I'd like a less generic confirmation message - Are you sure you want to permanently delete this blog?. But assuming this won't be possible without new translations, I feel that it's probably not worth it. Thoughts welcome.~

Closes #601. ~Ideally I'd like a less generic confirmation message - _Are you sure you want to permanently delete this blog?_. But assuming this won't be possible without new translations, I feel that it's probably not worth it. Thoughts welcome.~

👍 1 ❤️ 1

rfwatson がコメント (github.comから移行)

Not sure why the CI is failing

elegaanz (github.comから移行) がレビュー

elegaanz (github.comから移行) がコメント

Hello and thanks for your PR! Don't hesitate to change the message if you feel to do so, having one more string to translate is not a problem at all.

And the reason the CI fails is that it takes a lot of memory to compile Plume, and sometimes Circle CI containers just don't give us enough… so Rust is killed by the OOM-killer (so nothing to do with your code, it may work next time).

Otherwise, it works just fine. Thank you again!

Hello and thanks for your PR! Don't hesitate to change the message if you feel to do so, having one more string to translate is not a problem at all. And the reason the CI fails is that it takes a lot of memory to compile Plume, and sometimes Circle CI containers just don't give us enough… so Rust is killed by the OOM-killer (so nothing to do with your code, it may work next time). Otherwise, it works just fine. Thank you again!

rfwatson がコメント (github.comから移行)

Thanks!

Looking at the previous commits, would you recommend going on Crowdin directly to generate new translations?

I’ll play with this further tomorrow.

Thanks! Looking at the previous commits, would you recommend going on Crowdin directly to generate new translations? I’ll play with this further tomorrow.

elegaanz がコメント (github.comから移行)

You don't need to go on Crowdin to add translations: any string written in the i18n! macro is uploaded there automatically, and can then be translated (once your PR is merged, of course).

You don't need to go on Crowdin to add translations: any string written in the `i18n!` macro is uploaded there automatically, and can then be translated (once your PR is merged, of course).

codecov[bot] がコメント (github.comから移行)

Codecov Report

Merging #602 into master will increase coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #602      +/-   ##
=========================================
+ Coverage   34.54%   34.6%   +0.06%     
=========================================
  Files          67      67              
  Lines        7825    7840      +15     
  Branches     1881    1883       +2     
=========================================
+ Hits         2703    2713      +10     
- Misses       4361    4367       +6     
+ Partials      761     760       -1

# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/602?src=pr&el=h1) Report > Merging [#602](https://codecov.io/gh/Plume-org/Plume/pull/602?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/037674ae13849fb1f6357fd8a8b03ce8c7eda853?src=pr&el=desc) will **increase** coverage by `0.06%`. > The diff coverage is `n/a`. ```diff @@ Coverage Diff @@ ## master #602 +/- ## ========================================= + Coverage 34.54% 34.6% +0.06% ========================================= Files 67 67 Lines 7825 7840 +15 Branches 1881 1883 +2 ========================================= + Hits 2703 2713 +10 - Misses 4361 4367 +6 + Partials 761 760 -1 ```

rfwatson がコメント (github.comから移行)

You don't need to go on Crowdin to add translations: any string written in the i18n! macro is uploaded there automatically

Oh nice 😃

In that case I've updated this PR, and opened another to clarify the docs.

> You don't need to go on Crowdin to add translations: any string written in the i18n! macro is uploaded there automatically Oh nice :smiley: In that case I've updated this PR, and opened another to clarify the docs.

👍 1 ❤️ 1

elegaanz がコメント (github.comから移行)

Thank you again!

elegaanz (github.comから移行) が変更を承認

レビューア

プルリクエストは bffce041d7 でマージされています。

コマンドラインの手順も確認できます。

ステップ 1:

あなたのプロジェクトリポジトリで新しいブランチをチェックアウトし、変更内容をテストします。

git checkout -b feature/confirm_delete_blog master

git pull origin feature/confirm_delete_blog

ステップ 2:

変更内容をマージして、Forgejoに反映します。

git checkout master

git merge --no-ff feature/confirm_delete_blog

git push origin master

サインインしてこの会話に参加。

レビューアなし

マイルストーンなし

担当者なし

1 人の参加者

通知

期日

期日が正しくないか範囲を超えています。 'yyyy-mm-dd' の形式で入力してください。

期日は未設定です。

依存関係

依存関係が設定されていません。

読み込み中…

まだ内容がありません

ラベル マイルストーン

Confirm deletion of blog #602

Codecov Report

レビューア

ステップ 1:

ステップ 2:

ラベルマイルストーン