Add pull request branch configuration

[jmlemetayer]

This fixes #39

There is 2 new configuration:

• pull_request_branch: The pull request branch name.
• pull_request_unique: Is the pull request branch unique? If "false" the branch will be suffixed with a timestamp.

By default the branch is not unique and is suffixed with a timestamp, and the name is gh-actions-update.

The current default behavior is unchanged.

[saadmk11]

Thanks for creating the PR! 👍

By default the branch is now static, and the name is gh-actions-update.

I think we should not change current behavior (default) unless there is a big reason. The current behavior should be the default and the user can use pull_request_branch option to change the default behavior (e.g. branch name set by pull_request_branch will be used to create pull request or force push)

We also need to check if the pull request is already created or not with the users branch and only create pull request if it is not created, otherwise just force push.

[jmlemetayer]

Hi @saadmk11,

Did you had time to check the update of the PR ?

Best regards.

[saadmk11]

Did you had time to check the update of the PR ?

Sorry, I have been quite busy. I'll try to take a look some time next week.

[saadmk11]

Thanks for the updates. I have requested some changes.

We need to update https://github.com/saadmk11/github-actions-version-updater/blob/main/action.yaml with the input option.

[jmlemetayer]

Thanks for the updates. I have requested some changes.

I will edit the PR ASAP. Thanks for the review.

We need to update https://github.com/saadmk11/github-actions-version-updater/blob/main/action.yaml with the input option.

I wasn't aware of this file. I will update it as well. Thanks.

[jmlemetayer]

We need to update https://github.com/saadmk11/github-actions-version-updater/blob/main/action.yaml with the input option.

Done. I am unsure about the default value. I have set it to 'gh-actions-update-<timestamp>'.

[jmlemetayer]

PR updated with the requested changes. In theory it should work.

Do you have any way to test the feature before to merge it ?

[jmlemetayer]

Hi @saadmk11,

Quick reminder, could you test and review this PR? You might still be busy.

Best regards,
JM

[saadmk11]

Hi @jmlemetayer, Thanks for your work on this. For now I am merging the changes to a different branch as I need to do some manual testing.

[jmlemetayer]

Thanks, @saadmk11 I think I can also update one of my project using the action to use the development branch. I will keep you updated.

[jmlemetayer]

I have updated my project: https://github.com/jmlemetayer/project-release/

To use:

• The development branch: jmlemetayer/project-release@2f28645 (the pull_request_branch option was already pre-configured)
• And to run hourly: jmlemetayer/project-release@495410d

Also I have add jmlemetayer/project-release@63be594 as a possible workaround of the #49

[jmlemetayer]

Updated my project again, with the fix of the #49.

I let the action run twice, to see the pull request creation and update. Both run are a success:

• creation: https://github.com/jmlemetayer/project-release/actions/runs/3793304553/jobs/6450293101
• update: https://github.com/jmlemetayer/project-release/actions/runs/3793592424/jobs/6450852376

I have checked manually that the created pull request is correct and also successfully updated:
jmlemetayer/project-release#21

Looks good to me !