You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding or changing a cmdlet of the module, the documentation and parameter unit tests should be updated (see https://github.com/d365collaborative/d365fo.tools/wiki/Building-tools).
So far, this has been a manual task. To make this easier in the future, as a first step, I'd like to add a Github action that for now needs to be triggered manually. The action would execute the scripts to format the commend based help, update the parameter unit tests and update the documentation. If there are changes resulting from these scripts, the action would create a pull request for them.
In the future, this could be added to the action that validates pull requests and make the changes directly in the pull request branch.
Unfortunately, this does not work for pull requests from forks 😢
Reasons are explained in the use case description.
So until we find a different way to do this, the guidance would be that contributors should run the action in their fork repository against the branch that is used for their pull request.
We can also do it for them, but it is a bit round-about: First, we would need to pull their branch into the main repository or one of our forks. There, we can run the action, which creates a pull request with the changes. We would then merge that pr and then create a pull request from the modified branch back to their branch.
After adding or changing a cmdlet of the module, the documentation and parameter unit tests should be updated (see https://github.com/d365collaborative/d365fo.tools/wiki/Building-tools).
So far, this has been a manual task. To make this easier in the future, as a first step, I'd like to add a Github action that for now needs to be triggered manually. The action would execute the scripts to format the commend based help, update the parameter unit tests and update the documentation. If there are changes resulting from these scripts, the action would create a pull request for them.
In the future, this could be added to the action that validates pull requests and make the changes directly in the pull request branch.
See https://github.com/FH-Inway/d365fo.tools/actions/runs/5236416468/jobs/9453943953 for an example run of the action and FH-Inway#62 for an example of a pull request created by it.
The text was updated successfully, but these errors were encountered: