create-pull-request | pull request pointing to the base branch | REST library

If you look at the documentation of the create-pull-request action, it mentions that

Create Pull Request action will:

• Check for repository changes in the Actions workspace. This includes:
  • untracked (new) files
  • tracked (modified) files
  • commits made during the workflow that have not been pushed
• Commit all changes to a new branch, or update an existing pull request branch.
• Create a pull request to merge the new branch into the base—the branch checked out in the workflow.

It would always need an intermediary branch where it can commit the changes.

So if you modify your workflow config as below, adding the Reset master branch step to get the latest changes from the remote develop branch and reset the master branch, and specify branch: temp for the action, the workflow would create a temp branch with the same commits that you have pushed to develop branch and open a PR from temp to master branch. In subsequent commits to develop, it would keep on making the same changes to temp branch and open a PR similarly or update the existing PR.

The router module could be imported multiple times, as long as you define it only one time as root (RouterModule.forRoot(routes)). It is a common pattern to define the main router in a seperate file app-routing.module.ts and import it in app.module.ts. In addition, every feature module can have its own router module which will be defined as RouterModule.forChild(childroutes). The final result is that there will be only one instance of the router module where every modules contributes its own routes to the routing tree. I think in your case, you could just imagine your custom module as a 'feature'

There is VSTS CLI interface that you can configure to use git aliases (see this article), including creating pull requests.

Take a look at github's hub command. If you install it as documented, you can then open a pull request by running: