By bfuzze9898 on

I am trying to fork a repository (entity_events) and getting a generic error:

An error occurred while forking the project. Please try again.

I tried a different repository (address) and received the same error.

The console is showing network errors:

I don't see any way to add images to this post (really Drupal!?)

There are two errors:

  • Name: git-error - Status: CORS error - Type: xhr 
  • Name: git-error - Status: 404 - Type: Preflight

 

I don't know if this is specific to my account.  I'm not using a VPN and I am on a home/private network.

Please advise.

Comments

ressa’s picture

ressa
he/him
commented

Without knowing the actual commands it's hard to tell ...

bfuzze9898’s picture

bfuzze9898 commented

@ressa I'm doing this via Gitlab UI, not CLI.

ressa’s picture

ressa
he/him
commented

Thanks for clarifying, maybe you can describe the steps you take, like which URL, where you click etc.?

bfuzze9898’s picture

bfuzze9898 commented

Sure.

I went to https://git.drupalcode.org/project/entity_events

I clicked the 'Fork' button in the upper right.

I changed the project name from entity_events to entity_events_modules.  This automatically changed the slug to entity-events-modules.

I changed the namespace to my username.

All other options I left as default.

Then I clicked Fork Project button.

I see the loading icon and after a few seconds I see the error: 

An error occurred while forking the project. Please try again.

I repeated these steps for the address module and received the same error.

Thanks for your attention.

ressa’s picture

ressa
he/him
commented

Thanks for clarifying, I only think admins have that permission ... what is your end goal, after forking it?

Anyway, you probably have a better chance of an answer creating an issue in https://www.drupal.org/project/issues/drupalorg.

bfuzze9898’s picture

bfuzze9898 commented

I'm working on some entity-type specific events (e.g. user events).

I've forked other modules for bugfixes and enhancements.  Why would these modules be restricted?

Thanks.

ressa’s picture

ressa
he/him
commented

Is something preventing you from using the standardized workflow, of creating an issue, and from within that issue, click "Create issue fork", and follow the methods under https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... ?

PS. Can you link to a module, where you could fork it, with the method you described?

bfuzze9898’s picture

bfuzze9898 commented

Is something preventing you...

Not that I'm aware of.  That is how I have created forks in the past, but why have the GL Forks option if it is unavailable and why not have some clear error messaging.  Drupal seems to be making it hard to collaborate.  Wasn't that the lifeblood that kept D7 going for so long...

Thanks for the suggestions.  

ressa’s picture

ressa
he/him
commented

Sure, but as I see it, all systems have their quirks ...

I think once you try the new work flow, and get used to it, that it'll work out. In my opinion it's an improvement, over the old "attach a patch in a comment"-method, since you can now create an actual MR, get it tested automatically, and allow others to edit the MR, and many other features.

Eventually, all Drupal issues will move to Gitlab, which will of course streamline the process a lot.