From 162ede778085efcc8c919d83ff6f057afffb3c31 Mon Sep 17 00:00:00 2001 From: Yiheng Wang Date: Mon, 9 May 2022 19:33:06 +0800 Subject: [PATCH] update readme Signed-off-by: Yiheng Wang --- .gitattributes | 1 - README.md | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 .gitattributes diff --git a/.gitattributes b/.gitattributes deleted file mode 100644 index 9e0b393e..00000000 --- a/.gitattributes +++ /dev/null @@ -1 +0,0 @@ -segmentation/spleen_unet/models/model.pt filter=lfs diff=lfs merge=lfs -text diff --git a/README.md b/README.md index 04f80499..3179f50d 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ of the codebase named `[ticket_id]-[task_name]`. Ideally, the new branch should be based on the latest `dev` branch. 1. Make changes to the branch ([use detailed commit messages if possible](https://chris.beams.io/posts/git-commit/)). 1. [Create a new pull request](https://help.github.com/en/desktop/contributing-to-projects/creating-a-pull-request) from the task branch to the dev branch, with detailed descriptions of the purpose of this pull request. -1. For any large files inside the bundle, please use Git LFS commands to push them properly. +1. For any large files inside the bundle, please use [Git LFS commands](https://github.com/git-lfs/git-lfs/edit/main/README.md#example-usage) to push them properly. 1. Wait for reviews; if there are reviews, make point-to-point responses, make further code changes if needed. 1. If there are conflicts between the pull request branch and the dev branch, pull the changes from the dev and resolve the conflicts locally. 1. Reviewer and contributor may have discussions back and forth until all comments addressed.