Push the latest image on push master.

[liangyuanpeng]

Please briefly answer these questions:

• what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)

Push the latest image for let people can be experience the master branch function in advance.

• what changes does this pull request make?

• are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)

[mergify]

@liangyuanpeng You've modified the workflows. Please don't forget to update the .mergify.yml.

[mergify]

@liangyuanpeng Convert your pr to draft since CI failed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.59%. Comparing base (e35b35a) to head (5025f79).
Report is 49 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #802      +/-   ##
==========================================
+ Coverage   75.55%   75.59%   +0.04%     
==========================================
  Files         180      187       +7     
  Lines       26938    27563     +625     
  Branches    26938    27563     +625     
==========================================
+ Hits        20353    20837     +484     
- Misses       5366     5448      +82     
- Partials     1219     1278      +59     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Phoenix500526]

IMO, it's better to provide a script to build the latest image from the master branch rather than to build an image from the master branch and push it into our image repo. It will upload many images that are unstable to our image repo. It may not be a good practice.

[Phoenix500526]

@liangyuanpeng BTW, I am confused with these three workflows: merge_image.yml, release.yml, and docker_image.yml. The docker_image.yml workflow has not been triggered since it was created. Do you have any interest in refactoring them?

[liangyuanpeng]

It will upload many images that are unstable to our image repo.

It only "one" image---latest, the user should know that this is "The latest" image and not a stable image.

I would say this is a universal need. --> "I just want to use it and don't want to build it."

The docker_image.yml workflow has not been triggered since it was created.

I used this workflow to created the image for PR fix: xline watcher will loss event on my fork repo, see https://github.com/liangyuanpeng/Xline/actions/runs/8244904769

Do you have any interest in refactoring them?

please create a issue for it and i will pick it up when i have a time, or welcome everyone contribute.

[Phoenix500526]

LGTM