Created on 12 December 2023, 7 months ago
Updated 14 December 2023, 7 months ago

Add gitlab CI

📌 Task
Status

Closed: works as designed

Version

2.1

Component

Code

Created by

🇮🇳India deepakkm

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @deepakkm
  • Status changed to Closed: works as designed 7 months ago
  • 🇺🇸United States TR Cascadia

    This is spam.

  • 🇮🇳India deepakkm

    This is not a spam, we verified if there is any ticket open for all gitlab CI as it was release 3 months ago. But found none and hence opened a ticket. If you wish you can close the ticket anytime. Thanks

  • 🇺🇸United States TR Cascadia

    This module already has a .gitlab-ci.yml file, and Gitlab CI has been enabled for almost three months.

    You ran an automated script and opened an issue for something that did not need to be fixed, and you should have known it was not needed if you had done any kind of checking whatsoever. That is spam in my book, because you wasted my time by failing to do your homework before posting, and because you devalued the work I did in setting up Gitlab CI testing three months ago - you acted like my work didn't exist.

    If it were one post in one issue queue then that wouldn't be a problem because presumably you would learn from the experience and next time would check the project first before posting. But you posted the same thing simultaneously in 50 different issue queues requiring 50 different maintainers to respond to your automated script. That's no longer understandable, that's irresponsible.

    Your actions in running this automated script were not helpful - you didn't even bother to post a patch. If you had provided a patch, then you would have figured out for yourself that this project already has a .gitlab-ci.yml because your patch wouldn't have applied. Or you could have just looked at the project page and seen that this project is currently being tested with Gitlab CI.

    To me this feels all too much like the persistent problems we have with people trying to game the contribution credit system. Even if that doesn't apply in your case, your actions of using an automated script, not providing a patch, and failing to check before you posted amount to the same thing from my point of view.

    I would like to note for the record I asked you about this through your drupal.org contact form, and you chose to reply here in the issue queue.

Production build 0.69.0 2024