You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,6 @@ This is the process for committing code to the Scala project. There are of cours
9
9
1. Make sure you have signed the [Scala CLA](http://typesafe.com/contribute/cla/scala), if not, sign it.
10
10
2. Before starting to work on a feature or a fix, it's good practice to ensure that:
11
11
1. There is a ticket for your work in the project's [issue tracker](https://github.com/lampepfl/dotty/issues);
12
-
2. If not, create it first (perhaps given a thumbs up from the dotty-internals mailing list first);
13
12
2. The ticket has been discussed and prioritized by the team.
14
13
3. You should always perform your work in its own Git branch. The branch should be given a descriptive name that explains its intent. Some teams also like adding the ticket number and/or the [GitHub](http://github.com) user ID to the branch name, these details is up to each of the individual teams. (See below for more details on branch naming.)
15
14
4. When the feature or fix is completed you should open a [Pull Request](https://help.github.com/articles/using-pull-requests) on GitHub.
0 commit comments