Skip to content

docs: add workshop release download notice to README#142

Closed
Kalindi-Dev wants to merge 1 commit intoawslabs:mainfrom
Kalindi-Dev:main
Closed

docs: add workshop release download notice to README#142
Kalindi-Dev wants to merge 1 commit intoawslabs:mainfrom
Kalindi-Dev:main

Conversation

@Kalindi-Dev
Copy link
Contributor

Summary

Add an informational notice to the README directing workshop participants to download from the Releases page instead of cloning main.

Changes

  • Added a [!NOTE] block between the Table of Contents and Quick Start sections in README.md
  • The note links to the Releases page and clarifies that main may contain changes not yet included in a release

User experience

Before: Workshop participants could clone or download from main, potentially getting unreleased or unstable changes.

After: A visible note directs workshop participants to the Releases page for tested, stable versions, and sets expectations that main contains ongoing development work.

Checklist

  • I have reviewed the contributing guidelines
  • I have performed a self-review of this change
  • Changes have been tested
  • Changes are documented

Test Plan

  • Verify the [!NOTE] block renders correctly on GitHub
  • Verify the Releases page link resolves correctly
  • Confirm the note appears between the Table of Contents --- separator and the Quick Start heading

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

README.md Outdated
---

> [!NOTE]
> **For workshops, always download the latest release from the [Releases page](https://github.com/awslabs/aidlc-workflows/releases).** Release versions are tested and stable. The `main` branch contains ongoing development changes that may not yet be included in a release.
Copy link
Member

@scottschreckengaust scottschreckengaust Mar 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend:

Suggested change
> **For workshops, always download the latest release from the [Releases page](https://github.com/awslabs/aidlc-workflows/releases).** Release versions are tested and stable. The `main` branch contains ongoing development changes that may not yet be included in a release.
> **For workshops, download the latest release from the [Releases page](https://github.com/awslabs/aidlc-workflows/releases).** Release versions are tested and stable. The `main` branch contains ongoing development changes that may not yet be included in a release.

Copy link
Member

@scottschreckengaust scottschreckengaust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Kalindi-Dev
Copy link
Contributor Author

Modified the note to point to a pinned release as suggested by @harmjeff.
Excluded the word only as suggested by @scottschreckengaust

---

> [!NOTE]
> **For workshops, we recommend using a pinned release version.** The current recommended release is [v0.1.6](https://github.com/awslabs/aidlc-workflows/releases/tag/v0.1.6). The `main` branch contains ongoing development changes that may not yet be included in a release.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The README Quick Start section already guides the user to download the zip https://github.com/awslabs/aidlc-workflows?tab=readme-ov-file#quick-start and not clone the repo so this addition seems redundant.

Further, the notion of a workshop in the project's README seems a bit misplaced. I think it confuses an ordinary consumer of this repo what a workshop means. Suggest that the person coordinating an AI-DLC workshop reinforce such an instruction with participants offline.

Copy link
Contributor

@raj-jain-aws raj-jain-aws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The README Quick Start section already guides the user to download the zip https://github.com/awslabs/aidlc-workflows?tab=readme-ov-file#quick-start and not clone the repo so this addition seems redundant.

Further, the notion of a workshop in the project's README seems a bit misplaced. I think it confuses an ordinary consumer of this repo what a workshop means. Suggest that the person coordinating an AI-DLC workshop reinforce such an instruction with participants offline.

@harmjeff
Copy link
Contributor

The README Quick Start section already guides the user to download the zip https://github.com/awslabs/aidlc-workflows?tab=readme-ov-file#quick-start and not clone the repo so this addition seems redundant.

Further, the notion of a workshop in the project's README seems a bit misplaced. I think it confuses an ordinary consumer of this repo what a workshop means. Suggest that the person coordinating an AI-DLC workshop reinforce such an instruction with participants offline.

This change was meant to direct users who by default clone the repo to use release versions

@raj-jain-aws
Copy link
Contributor

The README Quick Start section already guides the user to download the zip https://github.com/awslabs/aidlc-workflows?tab=readme-ov-file#quick-start and not clone the repo so this addition seems redundant.
Further, the notion of a workshop in the project's README seems a bit misplaced. I think it confuses an ordinary consumer of this repo what a workshop means. Suggest that the person coordinating an AI-DLC workshop reinforce such an instruction with participants offline.

This change was meant to direct users who by default clone the repo to use release versions

If you're running into issues with this with workshop participants, suggest updating the existing statement "Download the latest release zip from the Releases page ..." to highlight the importance of downloading zip over cloning.

@Kalindi-Dev
Copy link
Contributor Author

Closing the PR based on the feedback!

auto-merge was automatically disabled March 25, 2026 14:10

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants