But now I have no idea how to set this from the outside without modifying the code directly. Is there a way to put this in the gitlab.rb config or another way to overwrite this value?
Designs
An error occurred while loading designs. Please try again.
Child items
0
Show closed items
GraphQL error: The resource that you are attempting to access does not exist or you don't have permission to perform this action
Since GitLab is used all over the world, it makes sense to be able to switch the time format. However, there is the case of a single GitLab installation being used by people with different time formats (e.g. GitLab.com). So, not only should there be an installation-level setting (e.g. on gitlab.rb), but also a user-level setting for users who that time format is not ideal (e.g. in User settings > Preferences):
I did a quick survey of the data we have for GitLab.com visitors for the current month to see which time format was prevalent (12h or 24h), but the result was a 50/50 tie. I assume that looking at a bigger time span wouldn't change the values too much. As there's no clear winner when surveying such a large installation as GitLab.com, we should stick with the current 12h format as the default value at the installation-level. After installing, admins can easily change it in the gitlab.rb file.
GitLab is moving all development for both GitLab Community Edition
and Enterprise Edition into a single codebase. The current
gitlab-ce repository will become a read-only mirror, without any
proprietary code. All development is moved to the current
gitlab-ee repository, which we will rename to just gitlab in the
coming weeks. As part of this migration, issues will be moved to the
current gitlab-ee project.
If you have any questions about all of this, please ask them in our
dedicated FAQ issue.
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to
rename gitlab-ce to gitlab-foss to make the purpose of this FOSS
repository more clear
I created a merge requests for CE, and this got closed. What do I
need to do?
Everything in the ee/ directory is proprietary. Everything else is
free and open source software. If your merge request does not change
anything in the ee/ directory, the process of contributing changes
is the same as when using the gitlab-ce repository.
Will you accept merge requests on the gitlab-ce/gitlab-foss project
after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in
gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git
remotes to use this new URL. GitLab will take care of redirecting Git
operations so there is no hard deadline, but we recommend doing this
as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?