- 19 5月, 2021 1 次提交
-
-
由 Advait Jain 提交于
-
- 18 5月, 2021 1 次提交
-
-
由 Advait Jain 提交于
These visibility changes are specific to the TFLM code in github.com/tensorflow/tflite-micro and would be awkward to upstream to github.com/tensorflow/tensorflow. Additionally, we are getting close to switching the current repository to be the source of truth for TFLM code and have thus made the decision to temporarily add some patches during the sync from upstream TF to the current repo. Manually tested that running `ci/sync_from_upstream_tf.sh` with the current change avoids reverting the changes from #73 (such as with #76).
-
- 15 5月, 2021 3 次提交
-
-
由 TFLM-bot 提交于
-
由 Advait Jain 提交于
Progress towards http://b/187830287
-
由 Advait Jain 提交于
keep @advaitjain as the sole codeowners for .github and ci
-
- 14 5月, 2021 1 次提交
-
-
由 TFLM-bot 提交于
-
- 12 5月, 2021 2 次提交
- 08 5月, 2021 1 次提交
-
-
由 Advait Jain 提交于
-
- 06 5月, 2021 1 次提交
-
-
由 TFLM-bot 提交于
-
- 05 5月, 2021 2 次提交
-
-
由 Advait Jain 提交于
This change will allow me to test the sync workflow.
-
由 Advait Jain 提交于
-
- 04 5月, 2021 2 次提交
-
-
由 github-actions[bot] 提交于
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
-
由 github-actions[bot] 提交于
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
-
- 03 5月, 2021 1 次提交
-
-
由 Advait Jain 提交于
Since we trigger the CI workflow on any label change, when the cla:yes label is applied the CI workflow will be run, and there is no way around that with the current setup. If the sync PR does not have the ci:run label, the checks will be skipped but will still need to be run again prior to merge since skipping the checks invalidates the previous completion of the required checks. As a result, we are keeping the ci:run label. What this means is that the reviewer can manually apply the cla:yes label and then start auto-merge (which will wait for another round of the required checks to be run).
-
- 01 5月, 2021 6 次提交
-
-
由 github-actions[bot] 提交于
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
-
由 Advait Jain 提交于
cla:yes can only be applied by someone from Google, so will be done manually. However, the goal here is to have the PR be ready to merge once a Google engineer reviews it.
-
由 Advait Jain 提交于
* Automatically remove the cla: no label and apply cla: yes label. * sync PR generation should not error out if there are no changes.
-
由 Advait Jain 提交于
-
由 github-actions[bot] 提交于
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
-
由 Advait Jain 提交于
-
- 30 4月, 2021 12 次提交
-
-
由 github-actions[bot] 提交于
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
Without the additional step of `git add`, any untracked files will not be part of the PR that is created with the sync workflow. Manually tested this change on my fork of tensorflow by removing a file, pushing it to main and then confirming that the sync workflow does not add to the PR prior to this change, but does add it to the PR after this change.
-
由 Advait Jain 提交于
Adding the cla: yes label seems error prone so we are going to stick to only applying the ci:run label automatically and manually toggle the cla status.
-
由 Advait Jain 提交于
This should allow the github script step to correctly apply and remove labels.
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
This reverts commit 2092fec8.
-
由 Advait Jain 提交于
For some reason the actions dashboard has stopped showing me the name of the sync workflow. Instead it is showing me the path to the yml file which is somewhat annoying.
-
由 Advait Jain 提交于
* Added a (presubmit) suffix to all the status checks that shold be required prior to merging. * trying out automatically removeing the "cla: no" label for the sync PRs.
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
-
- 29 4月, 2021 3 次提交
-
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
The corresponding change in upstream TF is: https://github.com/tensorflow/tensorflow/pull/48809 Bug: http://b/184884735
-
由 Advait Jain 提交于
-
- 28 4月, 2021 2 次提交
-
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
* The tests all pass when run locally, but fail when run via actions. * Removed readable_run and directly logging the build ouput since that is more convenient with github actions. * Separated the two Cortex-M tests into their own individual jobs.
-
- 27 4月, 2021 2 次提交
-
-
由 Advait Jain 提交于
-
由 Advait Jain 提交于
With #25 we went down a path that appeared at first to allow for the checks to be consolidated in an environment variable but ended up being quite complex. This PR instead modifies the per-job if check to either have the ci:run label or originate not from a pull request.
-