This is an automated email from the ASF dual-hosted git repository.
erisu pushed a change to branch chore/update-linter
in repository
https://gitbox.apache.org/repos/asf/cordova-plugin-file-transfer.git
omit f3bc2ae chore: update package-lock with 'npm update'
omit b06c33a chore: bump @cordova/eslint-config to 6.0.1
add 02dd05e chore(ci): draft release (#395)
add 2b330de chore: bump @cordova/eslint-config to 6.0.1
add dd9d5f7 chore: update package-lock with 'npm update'
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (f3bc2ae)
\
N -- N -- N refs/heads/chore/update-linter (dd9d5f7)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.npmignore => .asf-release/.gitkeep | 8 +-
.github/workflows/draft-release.yml | 155 ++++++++++++++++++++++++++++++++++++
.gitignore | 4 +
.npmignore | 3 +
.npmrc | 5 ++
5 files changed, 172 insertions(+), 3 deletions(-)
copy .npmignore => .asf-release/.gitkeep (80%)
create mode 100644 .github/workflows/draft-release.yml
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
