RapidFort Release 1.1.43
RapidFort Release 1.1.43 #53 (closed)
If this is your first merge, please use the Initialization Template.
For more information please visit Iron Bank Documentation
Note: Please be sure you create an issue related to this merge request and the issue is labeled StatusReview, this will initiate a CHT member review of your merge request.
Merge request reports
Activity
assigned to @nrupen_rf
Container Hardening Team
This merge request has been identified as not having an associated Gitlab issue.
In order to better facilitate you, we ask that you open up a Gitlab issue within the corresponding project using the appropriate issue template. See below for a list of issue types.
Issue types:
-
Application - Initial- Use this template if the container has never been added to the Iron Bank. -
Application - Update- Use this template if the container was previously added to the Iron Bank, but is being updated to a newer version. -
New Findings- Use this template if the container has not been updated but continuous monitoring has discovered new findings. -
Bug- Use this template for any verified container that has identifed a bug and/or potential fixes. -
Feature- Use this template for any verified container that is receiving a feature enhancement such as turning a feature on, not a version update.
Once you have created the issue, you must relate the merge request to the issue. You can do this by:
- Editing the merge request, and typing the
#character and then either type the issue number or select the issue from the list. - Do not prefix the
#character with anything, it should start on a line by itself. Particularly, do not usecloses #as the Gitlab issue may live on after this merge request has been resolved.
Note: Do not relate the merge request and issue any other way as those relationships will not be detected and this reminder will continue.
-
requested review from @rf_eve
assigned to @awarneritm
added StatusDoing label
mentioned in commit 79ade5ef
