Update markbind-action to enhance existing features

[tlylt]

Details of this PR has been posted & discussed in the main repo here.

Proposed commit message:
Update markbind-action to enhance existing features

The prerelease markbind-action has certain limitations such
as cannot specify the version of MarkBind to build files or
prevent force-pushing when updating the gh-pages branch.

Let's update it to a composite action and expand on the
existing functionalities to make this action more useful.
New configurations have been included to allow for flexibility
and support more use cases.

Using a composite action also makes it easier to maintain and
reuse existing actions.

[ang-zeyu]

Nice work, especially on the recipes.

Formatting wise, should we enclose workflow variables with double backticks for clarity? (e.g. 'gh-pages') Not a huge issue though, if the current looks nicer.

Just a few nits otherwise, mostly on the README:

[ang-zeyu]

For PR deployments (via Surge), the deployment will not be automatically deleted. This may be possible but the user will need to create another action to trigger the deletion on PR merge/close following this instruction. I guess I can create that as a reusable workflow and link the usage here so that users can choose to include that additional step if needed.

Sounds good, let's put up an issue for tracking. (if not attempting anytime soon)

Last few nits:

[jonahtanjz]

Nice work @tlylt!

Overall it looks good 👍 Just one suggestion :)

[tlylt]

@ang-zeyu @jonahtanjz Thanks for checking!

I think I have updated all the required stuff (let me know if there are any more issues).

For the release plan, according to this guide for Action release management, I think the steps will be:

• Fix any last issues within this PR
• Merge this into master
• Create a release/v2 branch from master for testing
• When ready, tag master as 'v2.0.0', and also 'v2', release on GitHub
• The 'v2' tag will be shifted everytime there's a new release of v2 level version

[jonahtanjz]

LGTM 👍

Let's wait for @ang-zeyu to approve as well :)

[ang-zeyu]

Lgtm 👍

Thanks for linking the guide as well!

[tlylt]

Seems like there's a regression possibly to some updates that I did in this PR such that the baseUrl input is not being handled properly if it is "". I will update here again once the issue is resolved.

[tlylt]

Sorry for the delay. I retested the three cases of baseUrl input and they all seem to work now. I think we are good to proceed with

Merge this into master
Create a release/v2 branch from master for testing

[jonahtanjz]

@tlylt Do you have write access to do the tagging and release?

Might also want to include a short commit message in the PR description :)

[tlylt]

@tlylt Do you have write access to do the tagging and release?

Might also want to include a short commit message in the PR description :)

I have added a commit message. I think I may not have the right to do so (I also don't think I can merge this PR).

[ang-zeyu]

@tlylt you should have permissions now : )