This is an automated email from the ASF dual-hosted git repository.
yasith pushed a change to branch feat/svclayer-portal
in repository https://gitbox.apache.org/repos/asf/airavata.git
discard a772a2d920 feat(portal): add Next.js frontend application
discard 6ddc5793d6 feat: migrate to REST API, remove Thrift, and clean up
legacy
discard 15a39c40db feat: add Spring Boot service layer architecture
discard d702ad9877 feat(db): add schema migrations, Flyway baseline, and DB
init scripts
add 00e28a7160 feat(db): add schema migrations, Flyway baseline, and DB
init scripts
add a8437e3a00 feat: add Spring Boot service layer architecture
add 3317aaea3c feat: migrate to REST API, remove Thrift, and clean up
legacy
new 7091feda55 feat(portal): add Next.js frontend application
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 (a772a2d920)
\
N -- N -- N refs/heads/feat/svclayer-portal (7091feda55)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../db/migration/airavata/V1__Baseline_schema.sql | 168 ++++++++++-----------
1 file changed, 84 insertions(+), 84 deletions(-)
