So I have copied from this one: https://github.community/t5/GitHub-Actions/GitHub-Package-Registry-with-Maven-causes-deployment-issues/m-p/39879

# This workflow will build a Java project with Maven
# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-maven
name: Java CI with Maven
on:

push:

branches: [master]

pull_request:

branches: [master]
jobs:

build:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v2
- name: Set up JDK 13
  uses: actions/setup-java@v1
  with:
    java-version: 13
- name: maven-settings
  uses: s4u/maven-settings-action@v2
  with:
    servers: '[{"id": "mixer", "username": "cryptearth", "password": "${GITHUB_TOKEN}"}]'
- name: Build with Maven
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  run: mvn -B package --file pom.xml

But isn’t there any other way than using some actiong someone provides for free - wich may could change at any time?

@cryptearth You could add settings.xml in the root path of your repo, you could refer to this article: 

https://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages#authenticating-with-a-personal-access-token 

You could use ${env.PASSWORD} in the settings.xml. 

<servers>
    <server>
      <id>github</id>
      <username>zhu5201314</username>
      <password>${env.PASSWORD}</password>
    </server>
</servers>

And in your workflow, add environment variable PASSWORD with the value of your personal access token stored in secrets. And add --settings parameter for mvn command. 

- name: Build with Maven
        env:
          PASSWORD: ${{ secrets.PackagePAT }}
        run: mvn -B package --file pom.xml --settings settings.xml

I noticed that you are using GITHUB_TOKEN for the password, in the official document, it is asked to use a PAT. 

@yanjingzhu thank you for your reply.

I noticed that you are using GITHUB_TOKEN for the password, in the official document, it is asked to use a PAT.

Do you have any sources from where you got that? As the doc you linked only links to another page only explaining GITHUB_TOKEN. I didn’t read anything about 

secrets.PackagePAT

Also: Although adding a settings.xml to the repo and specify it in the mvn command in the workflow may is a solution it would also mean that in each clone and fork of the repo it get copied around as well wich may could end up my username spreading around with me losing controll over it. I’d rather not want this to happen. Is there a way to mark a file to not get cloned/forked? In addition to this it will only work in the workflow. So if someone clones it and uses the --settings switch local for what ever reason it would break. I’d prefer to not break other peoples stuff.

@yanjingzhu Thank you very much. I just implemented what you recommended and it works fine.

NetBeans seem to have some shadowing issues as it blends in the ~/.m2/settings.xml instead of the project local settings.xml - but that doesn’t cause any issues with the git commit and push. The workflow goes green. This should be somewhere noted in the official doc.