-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use default branch instead of master for .doctrine-project.json #356
Conversation
5d9f6fd
to
8d1add5
Compare
There currently seems to be an invalid Github token that breaks the build. Because I don't have access to administer the Travis build and in favour of Github actions, There will be a new PR migrating out website build to Github actions. After the migration to Github actions, this draft can be finished as a PR. |
8d1add5
to
831b31d
Compare
The build with the default-branch seems to work now. The build is failing because the website files of the current default branches have outdated branch names. In the next days I'll create PRs to move the doctrine-website config from the master branches into the default branches. After all supported repositories by the website are covered, I'll change my draft into a PR and then it can be reviewed. |
2aae5cc
to
87e4752
Compare
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adds the website config to be compatible with the doctrine/doctrine-website#356 changes
87e4752
to
17965c5
Compare
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adds the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adds the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
All supported projects are covered with Pull Requests. Some of the projects are still on |
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
Adds the website config to be compatible with the doctrine/doctrine-website#356 changes
Adds the website config to be compatible with the doctrine/doctrine-website#356 changes
17965c5
to
1c73671
Compare
Adapts the website config to be compatible with the doctrine/doctrine-website#356 changes
1c73671
to
de50f76
Compare
Since the default branch feature of #356 was merged, it can't be assumed that a master branch exists for the target repository.
Since the default branch feature of #356 was merged, it can't be assumed that a master branch exists for the target repository.
Since the default branch feature of #356 was merged, it can't be assumed that a master branch exists for the target repository.
In order for the release workflow and changing branch names, this PR introduces fetching the .doctrine-project.json infos of each repository from the default branch instead of master.
Repositories that need to move the website config
.doctrine-project.json
to the default branch: