codecode
anyone good at helm charts / auto deploy? can you spot what i've done wrong in this MR that makes me unable to deploy a new chart with a DB_INITIALIZE? i can deploy a chart without one, and the MariaDB deployment works, but then i have to manually run the command i've put into DB_INITIALIZE
I'm running into consistent CI failures, even after rebasing off a commit on master that passed CI:
$ retrieve_tests_metadata
/usr/local/bundle/gems/gitlab-4.14.1/lib/gitlab/request.rb:84:in `authorization_header': Please provide a private_token or auth_token for user (Gitlab::Error::MissingCredentials)
from /usr/local/bundle/gems/gitlab-4.14.1/lib/gitlab/request.rb:50:in `block (2 levels) in <class:Request>'
from /usr/local/bundle/gems/gitlab-4.14.1/lib/gitlab/client/pipelines.rb:19:in `pipelines'
from /usr/local/bundle/gems/gitlab-4.14.1/lib/gitlab.rb:28:in `method_missing'
from scripts/api/get_job_id:41:in `find_job_with_filtered_pipelines'
from scripts/api/get_job_id:31:in `execute'
from scripts/api/get_job_id:103:in `<main>'https://gitlab.com/ethan.reesor/contrib/gitlab/-/jobs/868346255
@firelizzard_gitlab thanks for the alert! It looks like this is a known issue with a revert MR already created gitlab-org/gitlab#287674
Sorry for the inconvenience!
Is anyone else not able to fork https://gitlab.com/gitlab-com/www-gitlab-com?
The repository could not be imported. Every fork attempt has failed: Unable to fork project 22704850 for repository @hashed/fa/53/fa539965395b8382145f8370b34eab249cf610d2d6f2943c95b9b9d08a63d4a3 -> @hashed/4b/39/4b39b10f9dcc37663584c6afca61be4f3c039d6ec1564a598a669cb477dbad52: Failed to create fork repository. Please try again.
I've tried again a few times already
Hello Reviewers,
I have created an MR on a GitLab repo. May I know how long will it take to get merged/reviewed? Link is here: gitlab-org/gl-openshift/documentation!5
Thanks for your MR. There is not a specific timeline for reviewing an MR. However, since it's documentation I might be able to triage it later today. Cheers
Hello, I got forwarded to the Community Relations team from GitLab support.
I contribute regularly to GitLab by opening issues or commenting on them. Unfortunately, powerful triaging options are reserved for people with reporter permissions. I did not find anything on the web regarding whether it is possible for a non GitLab organization member to get this permission.
In order to help with smaller triaging tasks I'd like to request this permission. Currently it is sometimes a bit frustrating to have to ping GitLab memers and especially when they don't respond.
Is this the right place to ask about this or can you forward me to some more suitable place?
@claell there are some really good triage automations at GitLab which already automatically infer and apply stage, group, and category labels for issues and merge requests.
Besides that, some labels are also critical to indicate development state as well as priority and severity for issues. You can read more about this in https://about.gitlab.com/handbook/engineering/quality/triage-operations.
However, I agree it would be useful to allow community members to re-assign merge requests like it's described in gitlab-org/gitlab#16162. This could really help especially during hackathons, etc. /cc @cbacharakis_gitlab
@claell we certainly can help! Even just participating in discussions and referencing issues that could be related or duplicate is so much helpful. :basketball:
Labels: I think being able to add or change labels or even marking issues as related is not going to provide much value or help.
Planning: Regarding planning PMs are the DRI for what GitLab Engineering team members work on. You can read more about this in the product processes page in the handbook.
Contributing: In any case, community members are free to contribute a not-yet-existing feature under whatever license they prefer. You can read more about this in stewardship page.
Also, please don't let this discourage you from continuing to participate in issues and discussions but I think looping in team members arbitrarily like in https://gitlab.com/gitlab-org/gitlab/-/issues/5634#note_460620391 can easily slip between the cracks. If you want to continue looping in team members I'd suggest to first trying to identify the category each issue falls into and mention the product manager of the corresponding group. You can read more about this in depth in the product sections, stages, groups, and categories page. :heart: