Skip to content

Commit 5718642

Browse files
committed
Merge branch 'main' of https://github.com/flutter/demos into next-demo
2 parents 7f54084 + ea62e06 commit 5718642

File tree

2 files changed

+32
-1
lines changed

2 files changed

+32
-1
lines changed

CONTRIBUTING.md

+1
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,4 @@
22

33
This repo is for code that supports talks, blogs, and experiments. The code is unmaintained and presented "as-is". As such, the repo is not monitored for pull requests and/or issues, and you likely don't want to spend time contributing.
44

5+
**If you're on the Dash team at Google, and you want to add a new demo**, you're free to do so. There are no requirements.

README.md

+31-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,34 @@
11
# Dash Demos
22

3-
This repo is for code that supports talks, blogs, and experiments. **This code is unmaintained.**
3+
This repo is for code that supports talks, blogs, and experiments. **This code is unmaintained.**
44

5+
## Contributing
6+
7+
If you're on the Dash team at Google, this repo is appropriate for **any** demo, sample, experiment, etc that you don't want to commit to maintaining. This repository is a catch-all for code that just doesn't belong anywhere else.
8+
9+
For example:
10+
11+
- Demos for talks, events, workshops, or tied to a timeline in some way.
12+
- Sample apps that are in-progress.
13+
- Sample apps that are tied to experimental features.
14+
- Sample apps in which the running demo app is more important that the code itself.
15+
- Code that just doesn't belong anywhere else.
16+
- **Any code that shouldn't be advertised as having best practices or being up to date.**
17+
18+
## CI
19+
20+
This repository has CI in the case that you want to test your demo code against the three Flutter channels. **CI is not required to merge code,** it's simply here as a convenience. It's run every night at midnight, and when you make a PR.
21+
22+
To add your code to CI:
23+
1. For each Flutter channel, you'll find a CI file in the `/tool` dir called `flutter_ci_script_stable`, `flutter_ci_script_beta`, and `flutter_ci_script_master`. Open the file(s) that correspond to the channel you want to test your code against.
24+
25+
2. Add the directory name of your project to this array:
26+
```bash
27+
declare -ar PROJECT_NAMES=(
28+
# add projects here
29+
)
30+
```
31+
32+
## `_archive`
33+
34+
Projects can be moved here when they're no longer useful. This is purely cosmetic, and really only signals to readers that we no longer care about this code.

0 commit comments

Comments
 (0)