Commit f70e1d74 authored by mlncn's avatar mlncn 🛠

And when pushing also use Drupal branch

parent 675fbe0f
......@@ -140,7 +140,7 @@ Whenever creating a Display Suite field, configure to limit it to only the parti
* Initialize a git repository in the feature module. For example, `cd modules/contrib/drutopia_resource`, `git init`, `git checkout -b 8.x-1.x`, `git branch -d master`, `git add .`, `git commit -m "Create the Drutopia Resource feature"`.
* Go to the [Drutopia organization on GitLab](https://gitlab.com/drutopia/) and create a new project with the same folder/machine name as your feature module (or, if you do not have permissions in the Drutopia organization, start the project in your own namespace). Make it a public project (**Visibility Level** Public).
* Follow GitLab's instructions for an existing folder which we haven't already done; for example `git remote add origin git@gitlab.com:drutopia/drutopia_resource.git` and `git push -u origin master`.
* Follow GitLab's instructions for an existing folder which we haven't already done; for example `git remote add origin git@gitlab.com:drutopia/drutopia_resource.git` and `git push -u origin 8.x-1.x`.
## Adding permissions via config_actions
* Permissions are not directly exportable so they need to exported via config_actions.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment