Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
F
foodsharing
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
6
Snippets
Groups
Projects
Show more breadcrumbs
foodsharing-dev
foodsharing
Merge requests
!2850
fix release banner
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
fix release banner
fix-release-banner-date-check
into
master
Overview
0
Commits
2
Pipelines
2
Changes
2
Merged
Christian Walgenbach
requested to merge
fix-release-banner-date-check
into
master
1 year ago
Overview
0
Commits
2
Pipelines
2
Changes
2
Expand
Closes #____ (e.g.
#230 (closed)
)
What does this MR do?
How confident are you it won't break things if deployed?
Links to related issues
How to test
Screenshots (if applicable)
Checklist
added a test, or explain why one is not needed/possible...
no unrelated changes
asked someone for a code review
set a "for:" label to indicate who will be affected by this change
added to the next milestone (see
https://gitlab.com/foodsharing-dev/foodsharing/-/milestones
, unless it has a "for:Dev" label)
added an entry to
CHANGELOG.md
added a short text that can be used in the release notes
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum:
https://foodsharing.de/?page=bezirk&bid=734&sub=forum
. Please change the MRs label to "state:Beta testing".
Consider writing a detailed description
in German
.
Describe in a few sentences, what should be tested from a
user perspective
.
Also mention different settings (e.g.
different browsers
, roles, ...) how this change can be tested.
Be aware, that also
non technical
people should understand.
Release notes text in German
Edited
1 year ago
by
Christian Walgenbach
0
0
Merge request reports
Activity
All activity
Filter activity
Deselect all
Approvals
Assignees & reviewers
Comments (from bots)
Comments (from users)
Commits & branches
Edits
Labels
Lock status
Mentions
Merge request status
Tracking
Loading
Loading
Loading
Loading
Loading
Please
register
or
sign in
to reply
Loading