| Age | Commit message (Collapse) | Author |
|---|
|
Improve GraphQL Authorization DSL
Closes #57828
See merge request gitlab-org/gitlab-ce!25328
|
|
Previously GraphQL field authorization happened like this:
class ProjectType
field :my_field, MyFieldType do
authorize :permission
end
end
This change allowed us to authorize like this instead:
class ProjectType
field :my_field, MyFieldType, authorize: :permission
end
A new initializer registers the `authorize` metadata keyword on GraphQL
Schema Objects and Fields, and we can collect this data within the
context of Instrumentation like this:
field.metadata[:authorize]
The previous functionality of authorize is still being used for
mutations, as the #authorize method here is called at during the code
that executes during the mutation, rather than when a field resolves.
https://gitlab.com/gitlab-org/gitlab-ce/issues/57828
|
|
Docs: update code review guidelines
Closes #57305
See merge request gitlab-org/gitlab-ce!25460
|
|
Port design-management-vue-app to CE
See merge request gitlab-org/gitlab-ce!25494
|
|
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|
Markdown renderers find it easier to determine
where lists start and end when lists are surrounded
by new lines.
For consistency, also ensure entries in the list
are aligned when they span multipls lines.
|
|
|
|
Add "How to seed a database with millions of rows" section
See merge request gitlab-org/gitlab-ce!25439
|
|
'ce-9858-follow-up-on-a-bug-that-happens-when-using-a-factory-built-object-in-the-where-block-of-rspec-parameterized-tablesyntax' into 'master'
Fix and document an RSpec::Parameterized::TableSyntax edge-case
See merge request gitlab-org/gitlab-ce!25438
|
|
|
|
to relevant page names
|
|
|
|
|
|
|
|
Template and process improvements for documentation
See merge request gitlab-org/gitlab-ce!24315
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Use consistent language (end-to-end instead of integration).
Clarify purpose of `qa/specs/features/` vs. `spec`
|
|
|
|
# Conflicts:
# .gitlab/merge_request_templates/Documentation.md
|
|
issue
|
|
issues
|
|
Add a soft SLA for reviewers and maintainers
See merge request gitlab-org/gitlab-ce!25192
|
|
Update proofreader.md
See merge request gitlab-org/gitlab-ce!24943
|
|
For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.
|
|
|
|
This helped me troubleshoot
https://gitlab.com/gitlab-org/gitlab-ee/issues/9727#note_141202527.
|
|
|
|
|
|
|
|
[Docs] Improve the Review Apps documentation
See merge request gitlab-org/gitlab-ce!25161
|
|
Make danger pick reviewers and maintainers at random, for feontend,
backend, database, etc, changes, whenever files belonging to those
teams get changed.
|
|
- Add link to Event tracking in FE guides
|
|
Fix a typo in doc/development/documentation/styleguide.md
See merge request gitlab-org/gitlab-ce!25149
|
|
By setting expectations both the contributor and reviewer have more
certainty on what gets reviewed when, and at what speed changes could be
merged.
|
|
Documentation: Development guide for Kubernetes
See merge request gitlab-org/gitlab-ce!24618
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
|
|
Start writing some development guidelines in relation to our Kubernetes
integration
|
|
# Conflicts:
# .gitlab/issue_templates/Feature proposal.md
|
|
|
|
Instead of requiring one separate document for every version (which is
created by release managers), we now use a single document for both
Community Edition and Enterprise Edition. This allows developers to add
guidelines right away, instead of release managers having to determine
what to add.
Version specific upgrading instructions are placed in a separate
section. This prevents instructions from lingering around for many
versions should a developer forget to remove them. This also ensures
that all instructions are kept in a single place, instead of being
spread across different documents.
A minor downside is that CE and EE guidelines now live in the same
document, which could cause merge conflicts. Since we are working
towards a single codebase, this should only be an issue until we merge
the codebases together; something we expect to do in the coming months.
This commit also removes all old upgrading instructions, but these can
still be accessed using Git branch specific URLs (included in the
updating README).
|
|
Docs: correct word
See merge request gitlab-org/gitlab-ce!25065
|
|
|
|
|
|
Fix many 'when manual' anchors
See merge request gitlab-org/gitlab-ce!24947
|
|
Fix spelling and other minor improvements
See merge request gitlab-org/gitlab-ce!24813
|
|
docs: GitLab uses group milestones to handle issues
See merge request gitlab-org/gitlab-ce!24953
|
|
Update source installation to make it easier for release managers to work on releases
Closes gitlab-org/release/framework#113
See merge request gitlab-org/gitlab-ce!24967
|
