Skip to content

Instantly share code, notes, and snippets.

@sampathg9
Last active June 8, 2024 10:35
Show Gist options
  • Save sampathg9/fb25ff2b84b3f279417d to your computer and use it in GitHub Desktop.
Save sampathg9/fb25ff2b84b3f279417d to your computer and use it in GitHub Desktop.
Procedure to solve an issue on GIT repositories:

Procedure to solve an issue on GIT repositories:

  1. Firstly, we must update the code in our local system.

  2. Review the issues on GIT.

  3. When we click on issue, that issue will expand, after reading the issue put the status to this issue as ”S2 – In analysis”.

  4. Assign that issue to yourself on git.

  5. Update the status of that issue on GIT.

    • Issue on GIT comes with the status “S0 – Waiting” or “S1- Ready to start”.

    • If you are doing analysis on selected issue, put the status as “S2 – In analysis”.

    • If you are start working on an issue, put the status as “S3 – In development”.

  6. Before start to solve an issue, we must update the code in our local system.

  7. Find the issue where it comes from and why it comes.

  8. Then start to solve the issue.

  9. Test it properly and confirm that this issue has been solved.

  10. When ever you want to commit, stash the changes that you made and update(pull) the code before commit.

  11. After updating, apply the changes that you stashed.

  12. Make smaller commits while solving the issue.

  13. While committing the code , write comments on that issue and refer to the issue number on GIT.

  14. Push the code to appropriate GIT repository.

  15. Before pushing the code make sure “are you pushing code to correct sprint or not?”.

  16. Test the issue on dev server and confirm that “this issue is fixed”.

  17. Update the status to this issue on GIT with the label “S3.5 – Ready to Start – Internal”.

  18. Assign that issue to Project manager.

  19. Write comments to that issue as “This has been done” with screen-shots if that issue solved.

  20. If you have any doubts while solving the issue. Update the issue on GIT with proper understandable comments. Add the label “BLOCKED” and reassign it to Project manager.

@Eagle-dev01
Copy link

ok

@AmigosKazz
Copy link

thanks

@Mosespimor
Copy link

thanks for this insight.

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