-
Notifications
You must be signed in to change notification settings - Fork 49
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1395 from tripal/tripal3-readme-update
Update Tripal 3 README to reflect Tripal 4 release.
- Loading branch information
Showing
5 changed files
with
62 additions
and
53 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
name: Core Development Task | ||
about: For keeping track of Tripal 4 core development | ||
|
||
--- | ||
|
||
<!--- | ||
INSTRUCTIONS: | ||
Remember to tag this issue with 1+ groups it relates to. | ||
I suggest using the "Development Branch" section to the right once you create the issue. | ||
This links the branch to the issue and will automatically close the issue when the PR is merged. | ||
---> | ||
|
||
# Core Tripal 4 Development Task | ||
|
||
<!--- | ||
Fill out the branch name attached to this task below. The various tokens mean: | ||
- `tv4g[0-9]` indicates the functionality group the branch relates to. See tags for groups available. | ||
- `issue\d+` indicates the issue describing the purpose of the branch. By making a new issue for each | ||
major task before we start working on it, we give room for others to jump in and save you time if | ||
something is already done, beyond scope, or can be made easier by something they are working on! | ||
- `[optional short descriptor]` can be anything without spaces. This is meant to make the branches more | ||
readable so we don’t have to look up the issue every time. You are encouraged to only have one branch | ||
per issue! That said, there are some edge-cases where multiple branches may be needed (i.e. partitioned | ||
reviews) where variations in the optional short description can make the purpose of multiple branches clear. | ||
---> | ||
|
||
## Branch Name: tv4g[0-9]-issue\d+-[optional short descriptor] |
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
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
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