[APM2-625] update assets for mobile banking logo #257
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tookaa2
requested review from
new4762,
FhanOmise,
kan98,
aashishgurung,
hpariwat and
jutinapas
hpariwat
approved these changes
Apr 4, 2022
kan98
reviewed
Apr 4, 2022
jutinapas
approved these changes
Apr 4, 2022
new4762
approved these changes
Apr 4, 2022
kan98
approved these changes
Apr 4, 2022
FhanOmise
approved these changes
Apr 4, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Objective
Update logos to match mobile banking app
Related information:
Related issue(s): #< GitHub ticket number > (optional)
2. Description of change
Updated logos and labels according to request from product department
3. Quality assurance
Tested on staging api to ensure charge can be created
🔧 Environments:
Specify the details of your test environments, including, for each, the platform version (on which the plugin was run), the Omise plugin version, and the versions of your system software such as PHP or Ruby.
i.e.
✏️ Details:
Explain how to manually test this feature.
For example if changes were made in the UI or in the API, explain where and if any specific access is needed.
4. Impact of the change
List the steps that must be taken for this PR to work.
E.g.: rake yak:shave, Add "yak_key" to environment variables, ...
Be sure to include all systems that needs to be changed or which system is affected by the change
(Ex: Requires Elastic search to be installed and configured in secrets.yml).
Note: Please provide a screenshot if your changed impact to UI.
5. Priority of change
Normal
6. Additional Notes
Any further information that you would like to add.