Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why store build versions? #780

Closed
marcoscaceres opened this issue May 22, 2016 · 0 comments
Closed

Why store build versions? #780

marcoscaceres opened this issue May 22, 2016 · 0 comments
Labels
question

Comments

@marcoscaceres
Copy link
Member

I'm not sure why we are storing the build version in addition to .map file... it seems like it was a good idea at the time (I guess?), but now it just bloats the repo - I just did a checkout, and our current build directory is 117MB! If one wants a particular version of ReSpec, they can simply checkout the the tag, and run the builder.

I propose we put a stop to storing the ReSpec build version file and map file, and only have the common build.
marcoscaceres added a commit that referenced this issue May 26, 2016
@marcoscaceres
Merge branch 'develop' into gh-pages
3fd145a 
* develop:
  v3.2.127
  Chore(release): improve error reporting
  Fix(release): stop producing versioned files (closes #780)
  Fix(markdown): Space before quote (closes #786)
  v3.2.126
  Fix(markdown): don't add space after quot char
  Fix(utils): links space getting chopped off (closes #783)
  chore(package): update mocha to version 2.5.3
  Fix(inlines-spec.js): use spaces, not tabs
  Feat(global): implement proper PubSubHub
  Chore(package): update dependencies
marcoscaceres added a commit that referenced this issue May 26, 2016
@marcoscaceres
Merge branch 'develop' into gh-pages
ba4b585 
* develop:
  v3.2.129
  Fix(conformance): msg name typo
  Fix(pubsubhub): improve respecEvent deprecation warning
  Fix(legacy): Add messages for Aria/WebPayment specs (closes #793)
  Fix(save-html) Space after ( when saving(closes #786)
  v3.2.128
  v3.2.127
  Chore(release): improve error reporting
  Fix(release): stop producing versioned files (closes #780)
  Feat(builder): surface uglify warnings/errors
  Fix(pubsubhub): rewrite for..of using FP (closes #788)
  Fix(markdown): Space before quote (closes #786)
shikhar-scs pushed a commit to shikhar-scs/respec that referenced this issue Feb 19, 2018
@thomaschampagne @wlach
Add mouse out events on marker text (w3c#780)
1f96c15 
* Add mouse out events on Marker text
* Documentation for mouse over events on Marker text
* Change position of "Mouse Out Markers" in annotation documentation
@snyk-bot snyk-bot mentioned this issue Apr 1, 2021
Open
@snyk-bot snyk-bot mentioned this issue Aug 22, 2021
Open
@Bhanditz Bhanditz mentioned this issue Nov 14, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marcoscaceres