Skip to content

Conversation

@shogo82148
Copy link
Member

From Go 1.17, the go command understands //go:build lines.
https://tip.golang.org/doc/go1.17#build-lines
For more details on the syntax and migration plan,
see https://golang.org/design/draft-gobuild

What does this pull request do?

I installed Go 1.17 rc1 https://golang.org/dl/#unstable
and add //go:build lines by running go1.17rc1 fmt.

Where should the reviewer start?

How should this be manually tested?

Run go1.17rc1 vet.
From Go 1.17, go vet warns mismatched //go:build and // +build lines.
https://tip.golang.org/doc/go1.17#vet

nathany
nathany previously approved these changes Aug 2, 2021
@nathany
Copy link
Contributor

nathany commented Aug 2, 2021

@shogo82148 Would it be possible to add go1.17rc1 to the GitHub Actions test.yml file?

@shogo82148
Copy link
Member Author

Sure, I did.
Go 1.17 rc2 is just released https://twitter.com/golang/status/1422289882467164161?s=20
So, I add it instead of Go 1.17 rc1

@Code0x58 Code0x58 merged commit 16f0d42 into fsnotify:master Aug 4, 2021
ianyh pushed a commit to PreVeil/fsnotify that referenced this pull request Jan 19, 2022
* introduce GitHub Actions

* Add lint+vet+old versions to GitHub Action

* Remove Travis CI and references

* Drop support/testing for Go 1.11 and earlier (fsnotify#381)

* Update x/sys to latest (fsnotify#379)

* add //go:build lines + add 1.17.0-rc2 to test matrix (fsnotify#377)

* Update test matrix for go 1.17 stable release (fsnotify#385)

* Add AddRaw to not follow symlinks + Fix link folloing on Windows (fsnotify#289)

* v1.5.0 preparation (fsnotify#380)

* revise pull request template

* Revert "Add AddRaw to not follow symlinks + Fix link folloing on Windows (fsnotify#289)"

This reverts commit e2e9517.

* prepare 1.5.1, retract 1.5.0

* Removed dead link

* Update issue templates (fsnotify#410)

* Update issue templates

* remove old issue template

* Test on Go 1.18 and two most recent versions (fsnotify#411)

* Test on Go 1.18 and two most recent versions

* on push

* ci

* update readme

* revise contributing

* maintainers wanted

* Final Notice: Maintainers Wanted

* fix go vet warnings: call to (*T).Fatalf from a non-test goroutine (fsnotify#416)

* made the changes related to recursive directory check

* made changes in window.go for buffer size

* DA-992: Pair windows' delete + create event to generate a rename event (#1)

* made the changes related to recursive directory check

* made changes in window.go for buffer size

* added the oldname attribute

* old name added to rename event, one event is generated for rename

* added oldname in printing rename events

* tests for checking  the oldName attr for rename added

* create fsnotify event added

* input to create event changed

* create fsnotify event function modified

* ID added

* logs added

* added create fsnotify event in inotify

* logs added

* prints added

* reviews

* reviews addressed

* Hangkun/da 992/window rename event (#2)

* Let's begin

* Add getpath

* Init test workflow

* 1.40.0 exits?

* Linter fix

* asdf

* 100

Co-authored-by: hu13 <[email protected]>

* Clean up unused

* Badge

Co-authored-by: Hangkun Ung <[email protected]>
Co-authored-by: hu13 <[email protected]>

* Rebase upstream fixes

* Rename bundle only works on windows

* Update CI golang

Co-authored-by: Ichinose Shogo <[email protected]>
Co-authored-by: Oliver Bristow <[email protected]>
Co-authored-by: Nahum Shalman <[email protected]>
Co-authored-by: Nathan Youngman <[email protected]>
Co-authored-by: Loïc Vernet <[email protected]>
Co-authored-by: Nathan Youngman <[email protected]>
Co-authored-by: paris <[email protected]>
Co-authored-by: hu13 <[email protected]>
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.

3 participants