Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making Visual Changes (Enhancements/Improvements) #112

Open
nelsonic opened this issue Jun 22, 2019 · 0 comments
Open

Making Visual Changes (Enhancements/Improvements) #112

nelsonic opened this issue Jun 22, 2019 · 0 comments

Comments

@nelsonic
Copy link
Member

When making visual changes to our app(s) UI/Layout we need a systematic approach to ensure that the changes being made are needed (e.g: fixing a "bug" in the layout on mobile)
or

Steps to make visual enhancements:

  1. Capture a screenshot of the state before the change so that it's clear what needs to be fixed/enhanced. Paste the screenshot in an issue so we can refer back to it in any PRs.
    How to capture a screenshot: https://www.take-a-screenshot.org

  2. Follow remaining steps described in contributing guide.

  3. Include after screenshot to illustrate the effect of the change made in the PR.


We are always grateful for Pull Requests that enhance our projects but we need a much better way of communicating as a team/community to ensure effort/time is not wasted.

We recently received a PR that makes a visual change: dwyl/phoenix-chat-example#24
The PR doesn't reference an issue so it's difficult for the reviewer to understand it at a glance.
e.g: "Fixes visual regression in rendering messages because of upgrade to Phoenix 1.4 no longer using Bootstrap styles dwyl/phoenix-chat-example#19"
That means it takes longer for the PR to be reviewed/merged ... ⏳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant